This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: why is select=".[true()]" bad?
- To: xsl-list at mulberrytech dot com
- Subject: Re: why is select=".[true()]" bad?
- From: "John E. Simpson" <simpson at polaris dot net>
- Date: Mon, 04 Sep 2000 20:20:28 -0400
- Reply-To: xsl-list at mulberrytech dot com
At 05:01 PM 09/04/2000 -0600, Mike Brown wrote:
>Why is it that a predicate is not allowed when I do something like
>
><xsl:variable name="foo" select=".[@id=1]"/>
>
>I mean if the current node has an 'id' attribute numerically equal to the
>number 1, then $foo will be the current node; otherwise it will be an
>empty node-set, right? Both SAXON and XT gripe at me for having a
>predicate after . at all.
Guessing: Maybe because an ID-type attribute cannot have a numeric value?
(Completely unrelated to XPath and XSLT, of course -- an XML restriction.)
================================================================
John E. Simpson | "I spilled spot remover on my dog.
http://www.flixml.org | He's gone now." (Steven Wright)
simpson@polaris.net |
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list