AW: Bug or feature

Yes, $sort was declared and contained a string. I understand
that the variable definition causes no error. The point is that
with Xalan 1 I seem to end up with a variable which cannot be 
used, i.e. using $gummibaum in XPATHs then caused Xalan to
throw very deep (Java) stack traces. Probably the question
must go to the Xalan lists. I try one of those strictly 
forbidden crossposts...

> -----Ursprüngliche Nachricht-----
> Von: Oliver Becker [mailto:obecker@xxxxxxxxxxxxxxxxxxxxxxx]
> Gesendet am: Mittwoch, 25. April 2001 16:56
> An: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Betreff: RE:  Bug or feature
> 
> > > I mistakenly used
> > >
> > > <xsl:variable name="gummibaum"
> > >     ><xsl:value-of
> > > 
> select="substring(2,string-length($sort)-2,$sort)"/></xsl:variable>
> > >
> > > with a string containing variable $sort.
> > 
> > You mean that $sort wasn't declared?
> 
> Probably he meant $sort contains a string and not a number.
> In that case $sort would be converted to a number and evaluated to NaN
> (assuming this special string can't be converted to a number).
> According to http://www.w3.org/TR/xpath#function-substring
> (particularly the 4th example) I would expect that the result of this
> substring call is "".
> 
> If $sort *is* declared somehow then the processor mustn't 
> report an error.
> 
> Cheers,
> Oliver
> 
> 
> /-------------------------------------------------------------------\
> |  ob|do        Dipl.Inf. Oliver Becker                             |
> |  --+--        E-Mail: obecker@xxxxxxxxxxxxxxxxxxxxxxx             |
> |  op|qo        WWW:    http://www.informatik.hu-berlin.de/~obecker |
> \-------------------------------------------------------------------/
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 

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