[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Cost of complex match patterns

Subject: Re: Cost of complex match patterns
From: "Vladimir Nesterovsky" <vladimir@xxxxxxxxxxxxxxxxxxxx>
Date: Thu, 14 Aug 2008 02:39:58 -0700
Re:  Cost of complex match patterns
> > In Saxon, //bar is handled by an index, so exists(//bar) should be quite
> > fast after the first time (when the index is built).
> What about:
> <xsl:template match="foo">
>   <xsl:choose>
>     <xsl:when
test="ancestor::*/@type = 'a'">
>      ....
>     <xsl:when
test="ancestor::*/@type = 'b'">
> vs
> <xsl:template
match="foo[ancestor::*/@type = 'a']">
> <xsl:template
match="foo[ancestor::*/@type = 'b']">
> Would you say the two are
roughly equivalent, or are there other
> subtle differences?

In my opinion
it worth to resolve tasks in xslt in a way that 
is easier for human
It's an implementer's responsibility to run it smoothly.
Xslt is much more closer to a declarative language than to an assembler.
Vladimir Nesterovsky

Current Thread


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.