>At any rate, it's _always_ more efficient to avoid the creation of result >tree fragments, so you should always use this: > > <xsl:with-param name="arg1" select="substring(.,2)"/> > >instead of this: > ><xsl:with-param name="arg1"> > <xsl:value-of select="substring(.,2)"/> ></xsl:with-param> > >whenever you can. This is not a "special" use of xsl:with-param. Ok, "special" was the wrong term. I meant "another".
>By the way, don't underestimate the difficulty of tracking variables in a >complex language like XSLT -- it's not as easy as it might seem. Ups, I thought it would be very easy in XSLT, because no one can change the variable and if I leave the context, the variable will be destroied. >If you can post your document and stylesheet attached to a Bugzilla report, >I will use it when I start the RTF optimization work. Bug #7556. I have posted an example of using a variable with memory grow, too. > Dave Are you the only one managing Xalan-C? I would like to thank you for your work so far. Do you see any possibility to involve some other people improving Xalan-C? Xalan-C is a powerful and good thing. Many people using Xalan-C. I wouldn't like to see the stagnation of Xalan-C. HolgeR
