This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
why is select=".[true()]" bad?
- To: xsl-list at mulberrytech dot com
- Subject: why is select=".[true()]" bad?
- From: Mike Brown <mike at skew dot org>
- Date: Mon, 4 Sep 2000 17:01:11 -0600 (MDT)
- Reply-To: xsl-list at mulberrytech dot com
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