The following proposal comes to my mind :)
<xsl:context ref="nodeReference">
<xsl:call-template name="xx">
</xsl:call-template>
</xsl:context>
Here, the template "xx" get's a context as node, "nodeReference".
Such a feature is not needed, especially in XSLT 2, where the use of
<xsl:call-template> shouldn't be recommended -- why would anyone
prefer it to the use of <xsl:function> ?
Even in XSLT 1.0 <xsl:call-template> is not necessary -- one can
always accomplish the same with <xsl:apply-templates>.
--
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
---------------------------------------
To invent, you need a good imagination and a pile of junk
-------------------------------------
Never fight an inanimate object
-------------------------------------
You've achieved success in your field when you don't know whether what
you're doing is work or play
-------------------------------------
I enjoy the massacre of ads. This sentence will slaughter ads without
a messy bloodbath.
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--