RE: [xsl] xsl:variable question

["Long Zhao" <LZhao@xxxxxxxxxxxxxxxx>]

You are RIGHT!!!
but for the scope issue, i am right.

Long

-----Original Message-----
From: Thomas B. Passin [mailto:tpassin@xxxxxxxxxxxx]
Sent: Wednesday, December 19, 2001 5:23 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] xsl:variable question


Aside from the question about the scope of the variable, which Wendell
and
Joshua raised, there is a fundamental issue.  In the first example, you
assign a value "1" to the variable.  In the second, you try to assign a
nodeset consisting of elements named "1", which of course cannot exist
since
it would be illegal for an element name.  To make the second formulation
equivalent, you should write

<xsl:variable name="mode" select='"1"'/>

(that's '.."1"..' where I am inserting two dots to space out the inner
and
outer quotes for visibility).  This assigns the string value "1" to the
variable, just as in the first example.

Cheers,

Tom P


[Long Zhao]


here are two xsl files :

<xsl:template match="/">
<xsl:variable name="mode">1</xsl:variable>
......
</xsl:template>

<xsl:template name="dosomething">
<xsl:if test="$mode='1'">
.....
</xsl:if>
.....
</template>
------------------------------------
<xsl:template match="/">
<xsl:variable name="mode" select='1'/>
......
</xsl:template>

<xsl:template name="dosomething">
<xsl:if test="$mode='1'">
.....
</xsl:if>
.....
</template>

why the first one does not work, but the second one works.

am i doing anything wrong in the first xsl?




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


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