At 11:50 AM 21/07/2007 +0100, you wrote:
Now the questions is, is xsl:template name= ...
able to do something, which xsl:function cannot do?
Depends what you count as "able to do something". For example, a named
template can declare default values for parameters. Does that count?
Has is also be explained in this thread already that another difference is
that xsl:functions do not receive any initial focus?
And what about any difference between call named template and calling
a function, say via xsl:sequence select="blah(..)", with regard to
accessibility
to the static and dynamic contexts?
I thought I knew this stuff inside out but am now starting to get confused.
Isn't it true in some ways that calling named templates gives greater
access to static and/or dynamic context .. e.g. xsl:variables which may be
tunnelled or otherwise. So, in a sense, and apart from syntax differences,
isn't it true that calling a named template has a little bit more power than
calling a function, although possibly a moot point?
Thanks for a great discussion.
Justin Johansson
Now a Schema-Aware XSLT Evangelist
--~------------------------------------------------------------------
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>
--~--