Re: Dynamic XPath

> In terms of the standard - its would be good to have a function:
> 	findNode(String path)


If you look at the archives of the offical list for sending comments to
the WG you'll see several requests for a standard evaluate() function
(I think including one from me)

I suspect that the reason it was turned down is that having evaluate()
means that a lot more baggage is needed at run time. In a compiled
stylesheet execution the runtime system currently doesn't need an Xpath
parser or to know much about the namespace bindings used in the xpath
strings.  But if you have an evaluate function the runtime execution
system needs to have all the parsing machinery available. If you are
trying to fit XSLT on your mobile phone this might be a problem (although
apparently fitting 50 odd built in types and 1000 date functions is not
a problem...)

David


________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

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