This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Designs for XSLT functions (Was: Re: RE: syntax sugar for call-template)
- To: xsl-list at lists dot mulberrytech dot com
- Subject: Re: Designs for XSLT functions (Was: Re: [xsl] RE: syntax sugar for call-template)
- From: "Clark C. Evans" <cce at clarkevans dot com>
- Date: Fri, 23 Feb 2001 00:51:30 -0500 (EST)
- Reply-To: xsl-list at lists dot mulberrytech dot com
On Thu, 22 Feb 2001, David Carlisle wrote:
> J> as a non-recursive and fairly hacky solution.
> Hey I was going to post that:-)
> One man's (or woman's) "fairly hacky" is another's "more in
> the XSLT style"
Jeni's approach was very clever.
> Personally an xsl:append looks deeply suspect to me, if it's required
> for functions why isn't it required for the almost identical situation
> of binding node sets to variables? If it is also required for that
> is "append" the right concept for a declarative language, or should it
> be more like
> <xsl:variable select="foo[postion('some named construct corresponding
> to an xsl:sort setup') < 5]"/>
This seems like a 'XPath' style solution, not really a XSLT
style solution. *smirk*
Thank you both!
Clark
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list