-----Original Message-----
From: Carlos Barroso [mailto:est-c-barroso(_at_)ptinovacao(_dot_)pt]
Hy there.
I would lie to know which version is faster for the transformer:
in msxml you can use the commandline -t option
http://msdn.microsoft.com/webservices/building/xmldevelopment/xslt/default.aspx?pull=/library/en-us/dnxml/html/msxsl.asp#msxsl_timings
in saxon the commandline for timing is also -t
http://saxon.sourceforge.net/saxon7.6/using-xsl.html
so each XSLT processor has their own way to getting timing information....so
why not see for yourself....
Example 1:
<xsl:template match="/">
<xsl:for-each select="SITE" />
<p><a href="@url"></a></p>
</xsl_for-each>
</xsl:template>
by the way you forgot the curly brackets for shorthand
<xsl:template match="/">
<xsl:for-each select="SITE" />
<p><a href="{(_at_)url}"></a></p>
</xsl_for-each>
</xsl:template>
Example 2:
<xsl:template match="/">
<xsl:for-each select="SITE" />
<p>
<a>
<xsl:attribute name="href">
<xsl:value-of select="@url" />
</xsl:attribute>
</a>
</p>
</xsl_for-each>
</xsl:template>
In resume, what's faster: creating the text directly or using the
<xsl:attribute> for generating the text?
probably the difference in speed would be between the total number of bytes
being parsed, whereby the short hand would be slightly faster; but really this
type of example is easy for implementators to optimise and I would base my
choice on readability rather then some percieved hit in processing time.
there are plenty of other types of scenarios that have differences in speed,
such as recursion, google on benchmarking xslt and you will get a sense of
which processors are quicker, and what idioms are more effective ( or relevent
).
hth, jim fuller
This e-mail and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. If
you are not the intended recipient please contact the sender immediately. Any
disclosure, copying, distribution or any other use of this communication is
strictly prohibitedand may be unlawful. Stuart Lawrence Marketing
Communications Limited reserves the right to monitor and intercept
communications for unlawful business purposes.
This also confirms that this message has been swept for viruses, although
Stuart Lawrence Marketing Communications Limited accepts no responsibility for
any loss or damage resulting directly or indirectly from the use of this email
or contents.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list