On 03/09/2012 15:57, Costello, Roger L. wrote:
In other words, if I don't immediately output the results of
xsl:copy, then memory consumption grows and grows. Yes?
Potentially yes. But not really because of the xsl:copy, if you changed
it to xsl:sequence you'd probably get the same behaviour. If you are
using lots of variables and don't want them to take up space, you need
to have a very good idea how your xslt processor's optimiser works and
constrain your usage to uses which the optimiser can optimise away....
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>
--~--