(Resolved) "eval" should not be able to change DontDelete-ness of a binding

[lth]

(Really Brendan's bee, not mine, but the atrocity should be fixed anyhow.)

This is legal in ES3:

var v
eval("function v() {}")
delete v

It is legal because the introduction of the function by eval replaces the DontDelete binding of v with one that is deletable.

From https://bugzilla.mozilla.org/show_bug.cgi?id=395868 we have the following:

"""Relevant sections of the spec are: 10.1.3 where it states: "... If the variable object already has a property with this name, replace its value and attributes", and 10.2.2 with "Variable instantiation is performed using the calling context's variable object and using empty property attributes"."""

[brendan]

Thanks for filing this. It's not just a bee in my bonnet, but yours too ;-).

See https://bugzilla.mozilla.org/show_bug.cgi?id=395868#c14 where Florian Loitsch reports that no browser implements what ES1-3 specify here. That makes this a clear "bug fix" in the "de-facto standard trumps de-jure standard" sense, never mind the problems this poses for ES4.

/be

[lth]

I agree this seems like a clear bug fix candidate.