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: Uche Ogbuji <uche dot ogbuji at fourthought dot com>
- Date: Tue, 20 Feb 2001 11:18:32 -0700
- Reply-To: xsl-list at lists dot mulberrytech dot com
> > ("Every exsl:function must have an exsl:result within the
> > nodes in its descendant axis").
>
> Saxon says "every saxon:return element must have an ancestor saxon:function
> element". It doesn't say the converse: if no saxon:return is instantiated,
> the result is an empty string.
I think this is a better specification than what I suggested. Also neatly
solves the call-template problem, if we decide to allow call-template in
exsl:function.
+1 for giving exsl:result the same restriction.
--
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