W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2011

[Bug 12248] Make objects first-class API citizens

From: <bugzilla@jessica.w3.org>
Date: Sat, 05 Mar 2011 16:22:19 +0000
To: public-script-coord@w3.org
Message-Id: <E1PvuFH-00080o-AH@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12248

Brendan Eich <brendan@mozilla.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |allen@wirfs-brock.com,
                   |                            |brendan@mozilla.org

--- Comment #2 from Brendan Eich <brendan@mozilla.org> 2011-03-05 16:22:18 UTC ---
Why do we need such an unnaturally restricted object?

I've read the public-webapps thread and no one has made the case. Ojan et al.
cite precedent for allowing objects as keyword parameter sets. ES5 itself does
this, and ES5 specifies getters. Sicking listed running getters in a
well-defined order as a possible solution but no one said anything about this
idea.

The trick (such as it is) is to process parameters left to right, and normalize
object parameters by something like ES5's ToPropertyDescriptor abstract
internal operation (8.10.5 in ES5.1). If someone wants to write a getter and do
unusual things from it, that's their funeral.

/be

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Saturday, 5 March 2011 16:22:20 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:03 UTC