On 2007-12-03, at 15:56 EST, Donald Anderson wrote:
In LzRuntime.lzs:
[...]
seems like variable message may be undefined/uninitialied
at the ==> mark if Debug.uncaughtBacktraceStack is not set.
Indeed. Good catch. I replaced `message` with `errorString` (thus
overwriting the input parameter with an Object if I need to attach a
property to it). I think the brain-oh came from several false starts
at solving the issue another way.
Also, now that we have 'noteCallSite' nicely modularized,
it seems like super.xxx calls could also be registered in the stack
trace.
Maybe for future.
super calls already get the correct treatment, since they are
transformed into function calls (and re-visited, hence annotated there).
Thanks!
