Call for opinions: attribute defaults and renaming "flexible"
Mark S. Miller
erights at google.com
Wed Sep 3 22:51:50 PDT 2008
On Wed, Sep 3, 2008 at 9:49 PM, David-Sarah Hopwood
<david.hopwood at industrial-designers.co.uk> wrote:
> I don't see why any special case is needed here, or why removing it
> would require splitting [[Deletable]] from [[Configurable]].
> Suppose that [[Configurable]] = false prevents a writable data property
> from being deleted or changed to non-writable. What compatibility problem
> does this introduce? ES3 had no way for user code to change attributes,
> so I don't see how there can be a compatibility problem.
As I said in an earlier question from Ingvar on the same issue:
Legacy demands that new properties added to the global object by
assignment or top-level declarations start as non-deletable but
writable. But runtimes for secure subsets of ES, like ADSafe and Caja,
need to be able to freeze the global object of their frame during
their initialization. If not for legacy, we could make new properties
of the global object start as configurable. If deletable and
configurable were distinct, we could make new properties of the global
object start as configurable but not deletable. However, adding
another attribute to deal with this one problematic case seemed
overkill. Allowing non-configurable properties to be made non-writable
seems like the simplest adequate solution.
More information about the Es-discuss