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: Wed, 16 Mar 2011 17:43:45 +0000
To: public-script-coord@w3.org
Message-Id: <E1Pzul7-0000hL-Mm@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12248

--- Comment #33 from Boris Zbarsky <bzbarsky@mit.edu> 2011-03-16 17:43:43 UTC ---
> This continues to be a problematic restriction as we eventually intend to
> implement all DOM interfaces using ECMAScript native objects.

I think that would require some pretty major changes to the way all the various
web specs are being written.

For example, right now if interface Foo defines that member x is unsigned long,
then callees who take instances of Foo expect that the x they get is in fact
nonnegative.  If the implementation of the callee extracts the underlying C++
object from the ES object it has and calls into it directly, it has such a
guarantee.  If it needs to somehow deal with arbitrary props on the ES object
instead, then it needs to define a bunch of edge cases which are not defined in
any of the specs involved right now.

-- 
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 Wednesday, 16 March 2011 17:43:47 UTC

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