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 understanding. 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 http://www.nesterovsky-bros.com/
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format