W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2013

[Bug 23225] Let's start using class, not interface

From: <bugzilla@jessica.w3.org>
Date: Fri, 13 Sep 2013 16:09:00 +0000
To: public-script-coord@w3.org
Message-ID: <bug-23225-3890-xYmr0OmHSU@http.www.w3.org/Bugs/Public/>

Jonas Sicking <jonas@sicking.cc> changed:

           What    |Removed                     |Added
                 CC|                            |jonas@sicking.cc

--- Comment #12 from Jonas Sicking <jonas@sicking.cc> ---
I don't think we should allow

X implements SomeClass;

we should only allow

X implements SomeInterface;

I.e. classes should always have "interface objects" (aka "constructor
functions") and interfaces never have them. And only classes show up on the
prototype chain (with exception for weirdness on the global scope).

Interfaces would only be used as a construct for described shared APIs and for
when those shared interfaces are required in function arguments. I.e.
interfaces would only be used for

X implements SomeInterface;


  void fooFunction(SomeInterface arg);

You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 13 September 2013 16:09:05 UTC

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