Subj : Re: [SpiderMonkey] Error Reporter Failure (Read First)
To   : netscape.public.mozilla.jseng
From : Brian Barnes
Date : Sun Jan 30 2005 10:02 pm

On Jan 30, 2005, at 2:34 AM, Brendan Eich wrote:

Brendan, once again, thanks for the help.  You can ignore my other 
message, as I figured out a way around.

A quick note; I'm using spider-monkey scripts in "event" driven mode, 
i.e., they respond to events.   How and when they act on the events is 
hidden inside the implementation, therefore, I don't want to propagate 
because scripts are firing events, not branching to a new path (even 
though, inside the code, that's what is happening -- in the future, 
they could be stacked up, etc.)

So, I just did away with the error reporter hook; I have only one piece 
of code that calls all events.  I check for the return, if it's false I 
just do this:

	JS_GetPendingException(js.cx,&errval);
	report=JS_ErrorFromException(js.cx,errval);

This seems to work (scripts are guaranteed to only execute one at a 
time), and gets more all errors on a "per" event basis, which is what I 
want.

Thanks again, sorry for the misunderstanding about how errors work, but 
it actually allowed me to do this in a way that's better for my code.

[>] Brian

.