[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

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

Subject: why is select=".[true()]" bad?
From: Mike Brown <mike@xxxxxxxx>
Date: Mon, 4 Sep 2000 17:01:11 -0600 (MDT)
select where true
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

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.