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

[Bug 12458] Interface objects should be Functions

From: <bugzilla@jessica.w3.org>
Date: Thu, 14 Apr 2011 01:24:40 +0000
To: public-script-coord@w3.org
Message-Id: <E1QABIW-0005if-19@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12458

--- Comment #9 from Brendan Eich <brendan@mozilla.org> 2011-04-14 01:24:39 UTC ---
High order bit being interop does not automatically mean majority rules. There
is no interoperable de-facto standard now. We can get one by at least two
different paths.

The <builtin>.prototype object is a special case in JS already. It is never
instanceof <builtin>. It has a .constructor property referencing <builtin> but
that does not make it "is-a" in relation to the underlying class or interface
"type".

We need more detail about what "but clearly the interface prototype object does
not follow these rules either, nor should it IMHO" means. How does the
prototype of a DOM interface object *observably* differ from instances accessed
via that interface object or created by new'ing it?

/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 Thursday, 14 April 2011 01:24:42 UTC

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