Subj : Re: error handling in SpiderMonkey
To   : Forest Rankin <frankin@miramar.com>
From : Brendan Eich <brendan@meer.net>
Date : Mon Aug 11 2003 12:50 pm

Forest Rankin wrote:

>I believe you answered this by saying the parser doesn't have error
>recovery,
>

Correct.

> but I just wanted to clarify. I would like to be able to
>report all/most errors in the script at compile-time and runtime.
>

Compile and runtime *errors* stop the compilation or execution cold.  If 
you are seeing *warnings*, those do not stop either compilation or 
execution.  If a runtime error is caught as an exception, you won't see 
it unless you re-throw it and no one else catches it.

>In the mozilla browser you can open the JavaScript console which will
>display all the errors and warnings on the current page.
>

Are you sure you are seeing *all* the errors?  If you are not counting 
warnings as errors, then perhaps you are seeing different <script> tags, 
each of which has an error that is reported?  Each <script> tag is a 
separate compilation unit that is compiled and executed in turn, so each 
one may lead to one error report.  If you have a page with 20 <script> 
tags, you might see 20 errors, but that doesn't mean that SpiderMonkey 
is doing any error recovery (it isn't).

> I would like
>to do something like this but I can only get the JS engine to report
>one error. Does Firebird use Rhino and that's why it can report
>multiple errors?
>

No, Firebird is all C/C++/XUL/JS (no Java), it does not use Rhino -- it 
uses SpiderMonkey.

/be

.