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

Re: Figuring out easier readonly interfaces

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 17 Oct 2013 11:32:49 +0100
Message-ID: <CADnb78gO_SmxV0q57WoBtCsmS5fi2tRF-78v6XRjRxmBFf9pyw@mail.gmail.com>
To: "Mark S. Miller" <erights@google.com>
Cc: "Tab Atkins, Jr." <jackalmage@gmail.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Allen Wirfs-Brock <allen@wirfs-brock.com>, "Robert O'Callahan" <robert@ocallahan.org>
On Thu, Oct 17, 2013 at 10:15 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
> Assuming the subclass has access to private state, that does not seem
> surprising to me. The superclass only provides getters, the subclass
> extends the superclass by providing setters.
>
> I.e. the subclass augments the readonly API with a write API.

Never mind, I forgot the earlier part of this thread and
http://en.wikipedia.org/wiki/Liskov_substitution_principle et al. My
bad. Using mixins or some such would be more suitable here.


-- 
http://annevankesteren.nl/
Received on Thursday, 17 October 2013 10:33:17 UTC

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