Subject: RE: Re: Reference to variable cannot be resolved.
From: Américo Albuquerque <aalbuquerque@xxxxxxxxxxxxxxxx>
Date: Sat, 15 Feb 2003 14:55:46 -0000
|
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?
-----Original Message-----
From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
[mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Michael Kay
Sent: Saturday, February 15, 2003 8:27 AM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE: Re: Reference to variable cannot be resolved.
> I think the biggest problem here is that the scope of a
> variable is no longer obvious in these cases. This will also
> impose an (hidden) order of evaluation, which is not the most
> desirable feature for a non-imperative language.
The second sentence is nonsense. Variable references are resolved to
variable declarations at compile time, the run-time behavior doesn't
care in the slightest what the original name of the variable was.
Michael Kay
Software AG
home: Michael.H.Kay@xxxxxxxxxxxx
work: Michael.Kay@xxxxxxxxxxxxxx
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|