Hm... In catches, a new scope similar to one used with the "with" statement is created and added into the scope chain, containing only one property, the exception, by name specified in the catch statement. I wonder if there's maybe something missing with regard to activation of that scope in the debugger API callbacks.
Attila. -- home: http://www.szegedi.org weblog: http://constc.blogspot.com On 2007.12.24., at 14:34, David P. Caldwell wrote: > On Dec 24, 3:54 am, [EMAIL PROTECTED] wrote: >> Hello everyone, >> >> I am curious to know if anyone can help explain what is going on >> here? >> In the following snippet, if I set a breakpoint inside the catch >> block >> and then try to Evaluate the value of "e" in either the watches >> window >> or the eval window (using the debugger that ships with Rhino), I >> get a >> 'ReferenceError: "e" is not defined' error. Does anyone know why this >> is? I would have expected e to be dynamically added to foo() the >> minute the exception handling block was reached. Thanks in advance. > > Yes, I have run into this as well. A workaround I've been using is > similar to yours -- you can assign the exception to a local variable > in the catch block (like you do with errorObj) and then inspect -that- > object. > > -- David P. Caldwell > http://www.inonit.com/ _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
