Re: Designs for XSLT functions (Was: Re: [xsl] RE: syntax sugar for call-template)

[Uche Ogbuji <uche dot ogbuji at FourThought dot com>]

> Hi Uche,
> 
> > > So it would be plausible for us to specify an exsl:if() function that
> > > we want them implementers to implement and to write into that
> > > specification that the second argument must only be evaluated if the
> > > first argument is true, and the third argument must only be evaluated
> > > if the first argument is false.
> > 
> > The only thing to consider about this is that it introduces a side effect. 
> 
> No, it doesn't. However, in languages where you otherwise have
> side effects (like C) you have to think extra carefully about the
> evaluation order.

My exact point is that an exsl:if function as you describe above *does* 
introduce an order-of-execution side effect.  That is why if an exsl:ternary 
is debated, I would vote that all arguments must be evaluated regardless of 
the value of the selector.


-- 
Uche Ogbuji                               Principal Consultant
uche.ogbuji@fourthought.com               +1 303 583 9900 x 101
Fourthought, Inc.                         http://Fourthought.com 
4735 East Walnut St, Ste. C, Boulder, CO 80301-2537, USA
Software-engineering, knowledge-management, XML, CORBA, Linux, Python



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list