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

Maplike

From: Chris Wilson <cwilso@google.com>
Date: Fri, 13 Sep 2013 09:10:53 -0700
Message-ID: <CAJK2wqXnTh2ycUaixQMosNHywDjOR=eDkb2QhrOXrGP=z-Tj4w@mail.gmail.com>
To: public-script-coord@w3.org
Hey,

I was exploring Maplike to use in the context of the Web MIDI
API<http://webaudio.github.io/web-midi-api/>(which contains a pair of
unordered, keyed collections of MIDI ports
available to the UA), and I had a few questions I wanted to raise/ask the
status of.

First comment - the missing bits defining iterators in
http://dev.w3.org/2006/webapi/WebIDL/#es-map-members is, of course, a
little problematic, because I'll have to make something up.  Tab mentioned
the ES spec has these defined; should I go there for the definitions?

The second item is an explicit ask I have: Maps seem explicitly oriented
toward read/write collections; aka, in order not to violate the definition
of Map members, I will have to declare clear(), delete() and set() (and
explicitly say they do nothing, as you shouldn't be able to "remove" MIDI
ports, or some wiseass is going to ask how to restore them).

My hope is that it's feasible to say that any readonly attribute whose
value is a MapClass interface is automatically readonly with respect to the
map itself, such that set/clear/delete all throw or silently fail or
something.

Thoughts?

-Chris
Received on Friday, 13 September 2013 16:11:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:50 UTC