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

RE: XPath context reform?

xpath context 1
> Do you (or anyone else) have any particular thoughts on how
> context might have been better implemented?

I think an approach based on explicit range variables would have been less
error-prone, though it would have increased verbosity.

<xsl:for-each select="$node-set" as="$n" position="$p" size="$s">
 Node {$p} of {$s} has value {string($n)};

Of course it's too late to change it now. There are going to be new
problems, unfortunately, with the mixing of context item and range variable
concepts at XPath 2.0. But I think they are inevitable, you can't do a
general join without range variables.

Michael Kay
Software AG
home: Michael.H.Kay@n...
work: Michael.Kay@s...


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.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.

Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

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.