This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: [exsl] Naming exsl:return/exsl:result (Was: Re: Functional programming in XSLT)
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: Re: [exsl] Naming exsl:return/exsl:result (Was: Re: [xsl] Functional programming in XSLT)
- From: "Dave Gomboc" <dave at cs dot ualberta dot ca>
- Date: Tue, 20 Mar 2001 21:30:17 -0700
- References: <200103202135.QAA13700@biglist.com>
- Reply-To: xsl-list at lists dot mulberrytech dot com
> From: "Lassi A. Tuura" lat@iki.fi
[snip]
> Basically, why couldn't I say this?
>
> <xsl:call-template name="xref-to">
> <xsl:with-param name="node">
> <xsl:for-each select="document('glossary.xml')">
> <xsl:copy-of select="id($target)"/>
> </xsl:for-each>
> </xsl:with-param>
> </xsl:call-template>
[snip]
I think similarly about this (allow the return and manipulation of source
nodes in XSLT templates so that tasks such as set intersection may be
defined in XSLT) but people seem to think this would not only untenable but
even weird. Having neither the time nor the inclination to really dig into
the related issues myself (e.g. ramifications for other parts of XSLT,
interaction with XPath) like some others have, I just shrugged and went back
to my day job.
Dave Gomboc
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list