RE: Number error with XALAN

XT (incorrectly) allows you to have two different variables both called
"c"; Xalan (correctly) disallows it - though this is a very strange way
to report the error.

The code doesn't do what you think it does, even on XT - the person who
wrote it obviously thought they were incrementing the existing variable,
rather than declaring a new variable.

Michael Kay
Software AG
home: Michael.H.Kay@xxxxxxxxxxxx
work: Michael.Kay@xxxxxxxxxxxxxx 

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx 
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Sascha Assbach
> Sent: 20 January 2003 11:49
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject:  Number error with XALAN
> 
> 
> Hi there,
> 
> i have following problem
> in my XSL there is a section containing the following code, which ran
> without producing errors with XT
> but produces a "Can not convert #NUMBER to a NodeList!" error 
> with XALAN.
> 
> <xsl:variable name="c" select="1"/>
>   <xsl:for-each select="meldung....">
>     <fo:block font-size="10pt">...</fo:block>
>     <xsl:variable name="c" select="$c+1"/>
>   </xsl:for-each>
> </fo:block>
> 

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