[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Ordering of Blocks based on Input/Output
F> <xsl:if test="count($todo) > 0"> I>This test does the same as test="$todo", which is I>much more efficient for larger data Good point. Another optimizatioin is process all blocks that have their inputs already available - not just the first one: <!-- find first block $todo that has no inputs from any (other) block in $todo --> <xsl:variable name="next" select="$todo[. != $into/output/@block][1]"/> Francis picked this up with his second version which also introduced a key: <!-- find all blocks in $todo that have no inputs from the outputs of any (other) block in $todo --> <xsl:variable name="next" select="$todo[. != $into/output/@block]"/> I have to perform quite a few tests to come to a conclusion, but let me ask: what optimizations are likely to be performed by the XSLT processor? Are there general constructs that should be avoided? Regards, Dan __________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
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
|