Brendan Eich wrote: > On Oct 10, 2008, at 3:31 PM, Brendan Eich wrote: > >>> } catch (e) { >>> alert("caught " + e + " on " + x); >>> } finally { >>> alert("f called finally on " + x); >>> } >>> > > Skipping the intervening active finally clauses is bad, though -- a bug > in the current wiki rough draft that I should have mentioned. Dave will > post a follow-up soon.
The only sensible thing would be to run all of them; local "break" even does that in ES3. Of course that raises the question of what happens if a "break" whose matching activation frame is no longer live would generate an error but a finally clause would have caught and diverted it. Waldemar _______________________________________________ Es-discuss mailing list Es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss