However, the element that I just inlined may have a reference. So I
store the results into a variable and then repeat the process on the
content of the variable.
Why?
Why copy the whole thing rather than just apply templates and follow
references as you go?
I agree that is the way to go if there are no recursive references.
But if there are recursive references then that approach causes the program
goes into an infinite loop. My XML document has lots of complex, indirect
recursive references.
/Roger
-----Original Message-----
From: David Carlisle [mailto:davidc(_at_)nag(_dot_)co(_dot_)uk]
Sent: Monday, September 03, 2012 11:15 AM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Cc: Costello, Roger L.
Subject: Re: [xsl] Does <xsl:copy> use a lot of memory? Is there an alternative
that is more efficient?
On 03/09/2012 17:12, Costello, Roger L. wrote:
However, the element that I just inlined may have a reference. So I
store the results into a variable and then repeat the process on the
content of the variable.
Why?
Why copy the whole thing rather than just apply templates and follow
references as you go?
I don't see why you need any local storage or variables at all.
--
David
google plus: https:/profiles.google.com/d.p.carlisle
________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.
This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs.
________________________________________________________________________
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--