On 09/02/2012 07:59, TW wrote:
Do XSLT constructs maybe have an overhead that XPath ones don't?
Michael KnowsTheseThings, but I'll hazard an answer anyway. if you look
at Xquery syntax which is basically just an xpath-like syntax for parts
of XSLT, and the fact that saxon (at least) compiles xquery and xslt
(and xpath) down to the same internal representation, I would expect
that there is negligible difference in compilation time and literally no
difference in run time behaviour when the xpath and xslt are really
doing the same thing.
David
________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.
This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs.
________________________________________________________________________
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--