This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: RE: Designs for XSLT functions
- To: xsl-list at lists dot mulberrytech dot com
- Subject: Re: [xsl] RE: Designs for XSLT functions
- From: Joe English <jenglish at flightlab dot com>
- Date: Tue, 20 Feb 2001 08:17:02 -0800
- Reply-To: xsl-list at lists dot mulberrytech dot com
"Michael Kay" wrote:
>
> > > > I think clearly separating the specification of the abilities:
> > > >
> > > > -> to statically define and statically
> > > > invoke functions in XSLT, and
> > > >
> > > > -> to dynamically invoke functions
>
> I don't see any need for special syntax to invoke functions whose name is
> decided at run-time. That can easily be done using a general-purpose
> evaluate() extension that constructs XPath expressions from strings.
An apply() function (which simply calls another function whose
name is decided at runtime) would be easier to use than a general-purpose
evaluate() routine though. Programmatically constructing a syntactically
valid XPath expression can be tricky.
Apply() would likely also be easier to implement and more efficient
than evaluate().
--Joe English
jenglish@flightlab.com
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list