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

Re: Figuring out easier readonly interfaces

From: Allen Wirfs-Brock <allen@wirfs-brock.com>
Date: Wed, 2 Oct 2013 15:37:00 -0700
Cc: Boris Zbarsky <bzbarsky@mit.edu>, "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-Id: <3DCA151A-AC04-4B83-B194-76158B18287C@wirfs-brock.com>
To: Tab Atkins Jr. <jackalmage@gmail.com>

On Oct 2, 2013, at 2:25 PM, Tab Atkins Jr. wrote:

> On Wed, Oct 2, 2013 at 2:17 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
>> On 10/2/13 5:10 PM, Tab Atkins Jr. wrote:
>>> From what I can tell, the easiest way to do this is to use a Proxy
>>> around the mutable instance, which intercepts the "set" and
>>> "deleteProperty" traps (and maybe "defineProperty"?) and cancels them,
>>> and forwards the rest of the traps.
>> So directly .apply()-ing a setter gotten off the prototype would still
>> mutate the object?
> I don't think so, but I could be wrong.  I think that still ends up
> trying to do a "set" on the proxy, which'll get intercepted and
> cancelled.  It just takes a more circuitous route to get there.
> (I can't find the Proxy definitions in the latest HTML version of the


> ES spec, so I'm going on the most recent wiki page defining this stuff
> for now.  Publishing
Working draft
> specs as Word documents continues to be
> ridiculous.)
It's not clear how that relates to your inability to find the Prxoy material in the available HTML-based draft

Final ECMAScript standards are published in PDF and HTML.

Received on Wednesday, 2 October 2013 22:37:36 UTC

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