Bob,
Yet another reason to go with 2.0 if possible -- in 2.0 the key()
function takes a third argument by which you can dictate the context
in which the key should be called.
While this might not make an optimized processor any happier (though
it might), it's much nicer on the poor guy writing (and maintaining) the code.
Cheers,
Wendell
At 04:40 PM 9/6/2006, you wrote:
Which I seem to have done, without recognizing what a good idea it was. :-)
Neat, thanks.
On 9/6/06, Michael Kay <mike(_at_)saxonica(_dot_)com> wrote:
I generally find that if you're doing a join then it help to point a
variable at both the inputs, and avoid relying too heavily on context.
That still leaves the question of which should be your inner loop and which
your outer loop. If you use keys, or if your processor does join
optimization, it shouldn't matter too much.
--~------------------------------------------------------------------
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>
--~--