> Probably I should have made the node holding the expression
> and the node to use as the context node separate parameters.
> Michael Kay
Well, my misunderstanding is my own fault, as I should have read more
closely the first time. Still, if you wish to make things more obvious,
separate parameters would clarify the workings of the function. Perhaps
the parameter to specify the context node could be optional, with the
present behavior if no second parameter exists. That would keep code from
breaking when those of us who are using it now upgrade. However, I imagine
that you have many more pressing changes to make.
It's a great extension function, by the way. I was able to toss out a
nasty recursive template because of it. Of course, if I ever change
processors, I'll need that old template. But that's why there's version
I'm not planning to change XSLT processors, though. Saxon is definitely
best of breed, even without extras such as the evaluate-node function. I
very much appreciate your work.
Bryant Communication Services
(presently consulting at Synergistic Solution Technologies)