But this contradicts the fact that xslt doesn't run sequentially. For
the first variable to be shadowed by the second, the first has to be set
first. Why not the opposite? Why not the second being shadowed by the
first?
-----Original Message-----
From: owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
[mailto:owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com] On Behalf Of
Michael Kay
Sent: Monday, February 17, 2003 8:56 AM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: RE: [xsl] Re: Reference to variable cannot be resolved.
Hi.
Bu then how the compiler knows wish variable is the right one?
i. e.,
if I have:
<xsl:variable name="x" select="1"/>
<xsl:variable name="x" select="2"/>
when I do:
<xsl:value-of select="$x"/>
what will appear? 1 or 2?
2. The first variable is not in scope, because it is shadowed by the
second variable.
Michael Kay
Software AG
home: Michael(_dot_)H(_dot_)Kay(_at_)ntlworld(_dot_)com
work: Michael(_dot_)Kay(_at_)softwareag(_dot_)com
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list