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

RE: XPath's role (Was: Re: Re: . in for)

Subject: RE: XPath's role (Was: Re: Re: . in for)
From: "Michael Kay" <michael.h.kay@xxxxxxxxxxxx>
Date: Mon, 7 Jan 2002 22:03:07 -0000
RE: XPath's role (Was: Re:  Re: . in for)
> Taking the basic example:
>   for $item in $sequence return some:function($item)
> is equivalent to:
> <xsl:function name="my:for">
>   <xsl:param name="sequence" type="item*" />
>   <xsl:result select="if (empty($sequence))
>                       then ()
>                       else (my:function($sequence[1]),
>                             my:for($sequence[position() > 1]))" />
> </xsl:function>
OK, I'll change the rules. If removing range variables means that to achieve
simple things, people have to write recursive functions, then I'd rather
keep range variables!

Two reasons: Usability and Optimization. You can argue with both, of course,
but I think the solutions using range variables are more manageable both for
implementors and for users, especially the sort of users who've written a
bit of SQL.

Mike Kay

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Current Thread


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