This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: [exsl] Naming exsl:return/exsl:result (Was: Re: Functional programming in XSLT)


> 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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]