Re: [Edbrowse-dev] Error Legs

[Adam Thompson <arthompson1990@gmail.com>]

On Sun, Feb 09, 2014 at 09:48:57AM -0500, Karl Dahlke wrote:
> It is important not to stop javascript, even the current context,
> on a simple error like a syntax error or unreferenced variable.
> This happens a lot; some kind of analytics script
> that just tracks visitors to the site,
> and those tend to be complicated javascript,
> so uses a function that I don't have, and stops,
> but then the next chunk of code is executed,
> and that is the heart of the website, code that we really need to function.
> So this is one of those things I should think about for a couple days,
> before writing a line of code.

Yeah, I agree. I guess my point is more that when we have an unrecoverable
error we need to stop running the current script and possibly clean up the 
context.
However I really think we shouldn't allow js to kill the entire browser,
particularly if we want to get more people to use it.

Is there a way of killing the current script and then moving on to the next one?
The docs said something about throwing an uncatchable error within a c function?

Cheers,
Adam.