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: Tue, 12 Apr 2011 00:11:14 +0000
To: public-script-coord@w3.org
Message-Id: <E1Q9RCM-0004sj-0J@jessica.w3.org>

--- Comment #4 from Travis Leithead [MSFT] <travil@microsoft.com> 2011-04-12 00:11:13 UTC ---
I also worry about compat problems (though in IE9, we never tried implementing
interface objects as functions, so I have no specific examples).

In general, I'm not sure why we should consider this change, since there is
great interop here, and as Jonas mentions, you can discover "new-able"
interface objects by their type quite easily.

It may be obvious, but I'll also point out that not all objects created in the
global scope in ES5 are "constructors", for example "Math" is not a function.
(Of course, Math doesn't have a prototype either, so its another class of
object altogether.)

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 Tuesday, 12 April 2011 00:11:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:03 UTC