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: Mon, 19 Feb 2001 09:32:46 -0700
- cc: "Steve Muench" <Steve dot Muench at oracle dot com>
- Reply-To: xsl-list at lists dot mulberrytech dot com
> > I think clearly separating the specification of the abilities:
> >
> > -> to statically define and statically
> > invoke functions in XSLT, and
> >
> > -> to dynamically invoke functions
> >
> > would be useful. Some implementors may be interested in the former,
> > but not the latter, or vice versa.
>
> I do seem to be having trouble with terminology on this topic. By
> dynamic invocation do you mean something like
> exsl:function()/exsl:call()?
Yes, pretty much, but I'll note that I don't agree with Steve that there's any
need to separate them.
--
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