Subject: why is select=".[true()]" bad? From: Mike Brown <mike@xxxxxxxx> Date: Mon, 4 Sep 2000 17:01:11 -0600 (MDT) |
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. - Mike ____________________________________________________________________ Mike J. Brown, software engineer at My XML/XSL resources: webb.net in Denver, Colorado, USA http://www.skew.org/xml/ XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
XSLT/XPath Conformance - Call for i, G. Ken Holman | Thread | Re: why is select=".[true()]" bad?, Gary L Peskin |
Re: Built-in template rule for attr, John E. Simpson | Date | Re: why is select=".[true()]" bad?, Gary L Peskin |
Month |