significant rework to the 3K lines of code I already have. I currently don't
use for-each, I use various forms of "template match"
often it doesn't need much of a change if you are doing
<xsl:appy-templates select="something"/>
to select a pile of them in parallel, instead do
<xsl:appy-templates select="(something)[1]">
<xsl:with-param name="c" select="1"/>
</xsl:apply-templates?
to just process the first one, with a count of 1, and at the end of each
relevant template att an apply-template call to process the next in
line.
googling for xslt sibling recursion will turn up many examples,
including a thread from last month on this list.
Having said that, unless you _know_ you will hit memory constraints by
doing a second (or third) pass over the tree, that's easier to manage in
the long run.
David
________________________________________________________________________
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>
--~--