how does the experienced XSLT 2.0 programmer decide on
whether to use a xsl:function or a (named) xsl:template? Are
any performance issues involved (the processor I'm using is Saxon)?
Others have commented on usability aspects, and I agree entirely with what
they say.
As to performance, the Saxon implementation is probably optimized to support
that usage pattern.
In general, function calls in Saxon are more highly optimized than template
calls. For example, Saxon-SA will move the body of a function inline in some
circumstances, reducing the call overhead to zero and giving the opportunity
for further optimizations.
Michael Kay
http://www.saxonica.com/
When trying to comprehend a stylesheet, I find it easier if
the control-flow is managed by explicit function calls.
Using functions imposes the additional "burden" of passing
the node to work on, when compared to xsl:call-template.
However, passing the node brings the benefit of making the
"context" explicit.
Being able to use a function in XPath expression also offers
a less verbose invocation of functionality.
What are other benefits/shortcomings of either side? I
haven't found any documentation on this issue but would
appreciate any hints as to where to find some.
--~------------------------------------------------------------------
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>
--~--