Yes, it is global. My intention even was to do
<xsl:template match="$snode">
or
<xsl:template match="(//Menu)[number($pos)]">
but no can do, i'm in 1.0 (i recall it can be done in 2.0).
If i could do this i expected a speed increase, because i can just
copy evrithing without checking wath it is and just treat the one
selected...
Now i have to check for all Menu nodes if it's the one i want, and
there are currently 317 and counting...
I can't seem to think of anything else to improve this...
On Wed, 16 Feb 2005 21:49:12 -0000, Michael Kay <mike(_at_)saxonica(_dot_)com>
wrote:
It seems to improve a little if i change my test to
<xsl:when test="count($snode)=1 and count(.|$snode)=1">
where
<xsl:variable name="snode" select="(//Menu)[number($pos)]"/>
but not *that* much...
Is that a global variable or a local one? It should be global.
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
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>
--~--
--~------------------------------------------------------------------
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>
--~--