> That's why everything works fine in a debug build but goes to hell
in
> a release build :-)
>
> Yeah, I'll consider doing that but I'd also like to get a
> TraceListener event at the end of each executed template and, if I
add
> that feature, I will be able to build my own call stack anyway and
> won't be so tied to the implementation details of the VariableStack.
OK, I've thought of a bunch of modifications that I could make to be
able to infer a call stack. But I think that triggering an event when
an element is finished executing (call it traceEnd) is the best
because it is also potentially useful for other reasons e.g. a
profiler could use that information to decide how long it took for a
template (including it's children) to execute.
The only downside that I see is that every ElemTemplateElement will
have to have some boilerplate code inserted into it's execute method.
So:
1. does this seem like a good thing to do?
2. should this event only occur if XALAN_DEBUGGER_EXTENSIONS (my
define for indicating that debugging information is enabled) is set?
Cheers,
Brian
