Eval-invisible let bindings

Igor Bukanov igor at mir2.org
Thu Dec 6 03:25:42 PST 2007

On 06/12/2007, Lars Hansen <lhansen at adobe.com> wrote:
> Such an implementation only needs to detect direct
> uses of eval, as specified in ES3 and elaborated in ES4.   (ES4
> specifies the meaning of strictly more uses of eval than ES3, and
> requries that EvalError is thrown in other cases.)

This is good in theory, but for compatibility reasons the
implementation may be forced to support the indirect eval. For
example, at least recently some Goggle's pages contained var e=eval;
to compress the code. So I do not see how specifying more stricter
cases for ES4 would change the situation in practice. Hence this idea
to make at least new ES4 features immune from eval universality.

Regards, Igor

More information about the Es4-discuss mailing list