> >The only downside that I see is that every ElemTemplateElement will
> >have to have some boilerplate code inserted into it's execute method.
>
> Which could impose some performance impact even when trace is not in
> use...
> though I guess the right thing to do would be to prototype it and run
> benchmarks to check whether the penalty is acceptable.
I can always ifdef that code. All of my other patches so far are only
enabled if XALAN_DEBUGGING_EXTENSIONS (maybe I should change it to
XALAN_TOOL_EXTENSIONS?) is set. This functionality just seemed useful
for tools other than debuggers so I thought I'd see if anyone wanted it
to be available on all builds.
