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

RE: XPath context reform?

• To: <uche.ogbuji@f...>
• Subject: RE: XPath context reform?
• From: "Michael Kay" <michael.h.kay@n...>
• Date: Mon, 25 Mar 2002 16:14:50 -0000
• Cc: "'Mike Champion'" <mc@x...>,<xml-dev@l...>
• Importance: Normal
• In-reply-to: <200203251518.g2PFIGP00549@l...>
• Reply-to: <michael.h.kay@n...>

>
> 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)};
</xsl:for-each>

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...

• References:
  • XPath context reform?
    • From: Uche Ogbuji <uche.ogbuji@f...>

• Prev by Date: Re: Does XML-Dev matter?
• Next by Date: Re: XML in the alleged Real World (was Re: DoesXML-Dev m...
• Previous by thread: XPath context reform?
• Next by thread: Re: XPath context reform?
• Index(es):
  • Date
  • Thread