This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: why is select=".[true()]" bad?


Mike --

Try self::node()[@id=1]

The "." is an AbbreviatedStep (production [12]) and cannot be followed
by a predicate according to production [4].  That production requires

	AxisSpecifier NodeTest Predicate*

HTH,
Gary

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. I can't even say ".[true()]"! What's the deal?
> I don't see anything in XPath prohibiting this.


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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]