Hi,
Another argument for (2) is that an experienced XSLT developer can
read and understand the code much more quickly and maintain and modify
it more confidently. It exposes the logic better. This gets
increasingly important as things become more complex.
And it helps the inexperienced developer become more experienced more
rapidly in how to take advantage of XSLT's strengths.
These are not technical considerations, but they can be important ones.
Cheers,
Wendell
On Sun, Nov 4, 2012 at 5:06 AM, Вячеслав Седов
<schematronic(_at_)gmail(_dot_)com> wrote:
look like priority attribute can help in some cases - you can give
higher priority for frequent cases and lower priority for rare cases
i think in many cases power of using tunnel variables and next-match
underestimated by developers too
in many cases using other mode (even if it not necessary by logic)
help for speed also
--
Wendell Piez | http://www.wendellpiez.com
XML | XSLT | electronic publishing
Eat Your Vegetables
_____oo_________o_o___ooooo____ooooooo_^
--~------------------------------------------------------------------
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>
--~--