This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: XSLT 1.1 comments
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: RE: [xsl] XSLT 1.1 comments
- From: "Michael Kay" <mhkay at iclway dot co dot uk>
- Date: Thu, 15 Feb 2001 17:31:45 -0000
- Reply-To: xsl-list at lists dot mulberrytech dot com
> <saxon:function> looks just right, now I've looked it up.
>
> And I'm just hoping and guessing - again without research -
> that implementing this feature is largely syntax-sugar - and if not,
> let's make it optional.
>
It wasn't difficult to implement but it wasn't pure syntactic sugar either.
There were three things that needed care: using positional arguments instead
of named arguments in the call; preventing the function writing to the
output tree; and ensuring that lazy evaluation of node-sets still worked in
the case where a node-set was returned from a function. But apart from the
questions of data typing mentioned earlier (and those are no worse than any
other implications of data typing on XSLT), I don't think there are any
reasons to regard the facility as being risky, or bad coding practice.
Mike Kay
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list