This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: If vs. apply-templates for optional attributes


I'm doing the same test for many different elements....

I can't see how the named template gains me anything?  It doesn't make the
code any more compact,
and although the call to the named template likely adds no overhead, passing
the parameter might?  Moreover,
the test is still done. 

A smart compiler shouldn't have much more overhead for a modal template than
a named template, or am I missing something?

-----Original Message-----
From: Dunning, John [mailto:JDunning@goSPS.com]
Sent: Friday, June 07, 2002 9:57 AM
To: 'xsl-list@lists.mulberrytech.com'
Subject: RE: [xsl] If vs. apply-templates for optional attributes


If you're going to be using this type of test frequently (I'm not sure
whether you meant for the same element a dozen times or for a dozen
elements), you could use a named template with a parameter:

<xsl:template match="testelement">
	<xsl:call-template name="attTest">
	  <xsl:with-param name="node" select="."/>
	</xsl:call-template>
</xsl:template>

<xsl:template name="attTest">
<xsl:param name="node"/>
<xsl:copy>
	<xsl:if test="not($node[@attr])">
		<xsl:attribute name="attr">test</xsl:attribute>
	</xsl:if>
</xsl:copy>
</xsl:template>	

HTH,
John

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]