Good, so back to the original questions. Do we remove the current permission to throw EvalError? [I vote yes]
Once it's gone what do we do with the EvalError object? [I vote leave it in the spec. with a note that says it isn't currently used and exists for compatibility with previous ES editions.] >-----Original Message----- >From: Brendan Eich [mailto:[email protected]] >Sent: Tuesday, February 10, 2009 6:33 PM >To: Allen Wirfs-Brock >Cc: Waldemar Horwat; Chris Pine; es-discuss >Subject: Re: Is EvalError still needed? > >Chris Pine answered this one recently: > >https://mail.mozilla.org/pipermail/es-discuss/2009-January/008697.html > >/be > >On Feb 10, 2009, at 6:27 PM, Allen Wirfs-Brock wrote: > >> I've been told that Opera does (or at least did). However, Opera >> 9.63 on windows doesn't appear to. Maybe it's the mobile version >> that does it. >> >> Regardless, the clarification of the semantic difference between >> direct and indirect eval arguably makes the optional disallowance of >> indirect eval obsolete. Indirect eval would seem to have no utility >> (at least for web applications) if it is an "optional" feature. >> >> Allen >> >>> -----Original Message----- >>> From: Waldemar Horwat [mailto:[email protected]] >>> Sent: Tuesday, February 10, 2009 6:19 PM >>> To: Allen Wirfs-Brock >>> Cc: es-discuss >>> Subject: Re: Is EvalError still needed? >>> >>> Are there implementations that throw it? I thought there was at >>> least >>> one. >>> >>> Waldemar >> >> _______________________________________________ >> Es-discuss mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/es-discuss > _______________________________________________ Es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
