I am using -
<xsl:variable name="..." >
<xsl:copy-of select="...." />
</xsl:variable>
in my code. Do you think this hampers performance?
Yes.
It is much better to go <xsl:variable name="..." select="..."/> if that
is what you mean, that essentially just makes a variable that references
into the input node set, whereas xsl:copy has to make new nodes with
new identities.
similarly
<xsl:variable name="x" select="2"/>
makes $x the number 2 but
<xsl:variable name="x">2</xsl:variable>
makes $x a result tree fragment corresponding to a node set consisting
of a root node containing a child text node with value the string "2".
This is harder to build and harder for the system to coerce back to
being the number 2 when you use it.
David
________________________________________________________________________
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