This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Designs for XSLT functions (Was: Re: RE: syntax sugar for call-template)
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: RE: Designs for XSLT functions (Was: Re: [xsl] RE: syntax sugar for call-template)
- From: "Michael Kay" <mhkay at iclway dot co dot uk>
- Date: Wed, 21 Feb 2001 00:34:41 -0000
- Cc: <uche dot ogbuji at fourthought dot com>
- Reply-To: xsl-list at lists dot mulberrytech dot com
> It's crucial that the conditional operator only evaluates one
> of it's clauses.
> Otherwise you could not use it for recursive functions. Also you would
> need that behaviour particulary when one of the claues had a
> side effect
> (using the more common definition :-).
It's also important where one branch will cause an error. This is why XPath
defines order of execution for "and" and "or". It means one can safely write
if (function-available('exsl:eval'), xsl:eval('magic'), '****')
Mike Kay
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list