W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

[WebIDL] platofmr array objects

From: Andrew Oakley <andrew@ado.is-a-geek.net>
Date: Wed, 13 Jul 2011 12:45:43 +0100
Message-ID: <4E1D8567.1020002@ado.is-a-geek.net>
To: public-webapps@w3.org
> Platform array objects defy being fixed; if Object.freeze,
> Object.seal or Object.preventExtensions is called on one, the
> function MUST throw a TypeError.

Can I ask why?  I don't see any reason for this and it feels like it
would make implementations more complicated.  (This also seems to be
present in the platform objects description.) Platform array object [[GetOwnProperty]] method says that the
property descriptor for "length" whould have [[Configurable]] set to
true.  Later on we try to make sure it can't be deleted (
Would it not be easier just to make it not [[Configurable]]?

The [[GetOwnProperty]] implementation also tries calling the normal
version of [[GetOwnProperty]] at the end of the algorithm rather than at
the start like Array and Arguments objects.  I could agree with it being
either way round, but it would be nice to be consistent with the
ECMAScript spec.

Finally, we don't define what "Reject" means here (although we do define
it for the "platform object" algorithms.

Andrew Oakley
Received on Wednesday, 13 July 2011 11:58:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:22 UTC