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

[Bug 27354] Internal slots

From: <bugzilla@jessica.w3.org>
Date: Wed, 22 Apr 2015 19:50:18 +0000
To: public-script-coord@w3.org
Message-ID: <bug-27354-3890-H9JUJuwGlX@http.www.w3.org/Bugs/Public/>

Tab Atkins Jr. <jackalmage@gmail.com> changed:

           What    |Removed                     |Added
                 CC|                            |jackalmage@gmail.com

--- Comment #11 from Tab Atkins Jr. <jackalmage@gmail.com> ---
(In reply to Anne from comment #10)
> (In reply to Ian 'Hixie' Hickson from comment #8)
> > - We already have the equivalent readable way to do this; HTML does it all
> > over, for example. You just say that "A Foo object has a bar state" and then
> > define things in terms of a bar state. (It's indeed a mistake to do this by
> > reusing the names of exposed attributes; don't do that.)
> This gets very verbose though, e.g. for Event. Currently Event and its many
> subclasses do not do this and instead rely on some implicit understanding of
> internal slots. I think it would be much better if we started making that
> concept a) explicit and b) easy to work with by having IDL do a bunch of it
> for you.

In particular, Bikeshed makes this easy to talk about - it recognizes
attributes named like "[[Foo]]" as private slots.  You just have to define them
manually, rather than putting them in the WebIDL, currently.

You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 22 April 2015 19:50:19 UTC

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