[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Designs for XSLT functions (Was: Re: RE: syntax su
> > I'd say "scary thought: no", but how to best restrict this? > > Structurally? ("Every exsl:function must have an exsl:result within > > the nodes in its descendant axis"). > > There's a good point there about what to do if no exsl:result element > is instantiated. Returning an empty node set would at least stop > function calls from breaking if the result of the function was used as > a node set. Or should it be an unrecoverable error if no exsl:result > is instantiated? I don't mind saxon:functions's answer to this: the result is an empty string in the absence of exsl:result -- Uche Ogbuji Principal Consultant uche.ogbuji@xxxxxxxxxxxxxxx +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
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|