Well, the "else" part is cut&paste, so i'm not writing more code... but
the important here is the execution of code without necessity, so i'll
change to the choose/when/otherwise.
Your sugestion of using
<xsl:value-of select="number(parent::menu=(//menu)[$pos])"/>
is very neat. However i cant use it cause the "otherwise" is not 0 but
instead the prior value of the node, that could be 1 or 0.
But ofcourse, you could not guess that...
Thanks again.
Michael Kay wrote:
As a side question, i tend to make things like
<xsl:if test="parent::menu=(//menu)[$pos]">
<xsl:text>1</xsl:text>
</xsl:if>
<xsl:if
test="not(parent::menu=(//menu)[$pos])">
<xsl:text>0</xsl:text>
</xsl:if>
Is there any drawback in doing this insted of choose/when/otherwise?
Yes, you're writing more code and the XSLT processor is executing more code.
In fact, assuming you've got the boolean condition right, you could replace
this whole thing by
<xsl:value-of select="number(parent::menu=(//menu)[$pos])"/>
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--