W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2014

Re: Determining what prototype should be used for an object

From: Anne van Kesteren <annevk@annevk.nl>
Date: Mon, 17 Nov 2014 13:58:48 +0100
Message-ID: <CADnb78hFXwgsr86rgFxnREqBtjDgAw2vEgiR0JHG+zuWG=-_tw@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: Allen Wirfs-Brock <allen@wirfs-brock.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Ian Hickson <ian@hixie.ch>
On Sun, Nov 16, 2014 at 6:55 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> This problem, of course, never arises in ES so far, since it's a monolithic
> spec.

I see what you're saying. Part of this is why I suggested that maybe
we should move to a world where the internal slots are more explicit.
That way a node would have an internal slot allocated to a NodeList
which cannot be null, and therefore you can derive it has to be
created along with the node. (And when I say derive, I mean that I
would expect that to be spelled out in IDL of course.)

Additional I have the hope that describing internal slots in a
consistent way helps people more clearly think about the kind of APIs
they are introducing and how they fit together. Perhaps naïve.

Received on Monday, 17 November 2014 12:59:15 UTC

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