This means that elimination of node-set
means impact on performance,
Whether the absence of RTF type in XSLT impacts on performance
presumably depends on what you were doing to get round the restriction
in XSLT1.
As I don't really like using extension elements (even x:node-set()) for
portability reasons, I routinely go
<xsl:variable name="x">
<stuff>
<here/>
</stuff>
</xsl:variable>
...
... select="document('')/*/xsl:variable[(_at_)name='x']/stuff/here" ..
which causes the entire stylesheet to be reparsed as an input document
and built as a node tree, just for me to extract this variable, not to
mention that on the original processing of the stylesheet the rtf
variable x was built never to be used at all.
I'm assuming that in XSLT2
... select="$x/stuff/here"
will be much more efficient.
David
--
http://www.dcarlisle.demon.co.uk/matthew
________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list