Subject: Re: [xsl] parameters in XSLT 2.0 From: Bruce D'Arcus <bdarcus@xxxxxxxxx> Date: Wed, 8 Jun 2005 23:55:42 -0400 |
For example, first I have this variable to suck in outside data:
<xsl:variable name="raw-biblist"> <modsCollection xmlns="http://www.loc.gov/mods/v3" xmlns:bib="http://purl.org/NET/xbiblio/citeproc"> <xsl:copy-of select="$bibrecord/*/mods:mods"/> </modsCollection> </xsl:variable>
It's certainly not obvious that copying the source data in this way is achieving anything useful.
Possibly: I can't see what the apply-templates calls are doing, so it's hard
to tell. If the apply-templates calls are creating new elements, then
there's probably no extra cost (in fact it may be cheaper) to wrap these
elements in a document node (a temporary tree). If there's a saving to be
made, then it will be made by avoiding creating new nodes (or copying
existing nodes).
Two things are worth remembering about performance engineering:
(a) don't tune your code unless it is failing to meet its performance requirements.
(b) the only way to know whether your tuning attempts are worthwhile is to
make measurements before and after.
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] parameters in XSLT 2.0, Michael Kay | Thread | Re: [xsl] parameters in XSLT 2.0, David Carlisle |
Re: [xsl] To avoid converting html , Ahsan Ali | Date | Re: [xsl] What is exciting in XSLT , Mukul Gandhi |
Month |