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

Re: All ECMAScript attributes should be non-configurable

From: Erik Arvidsson <arv@chromium.org>
Date: Tue, 11 Oct 2011 12:13:46 -0700
Message-ID: <CAJ8+GojSp=PgvgpwiqbK-BRa9wQphMdrJOYgy2O-93=oR_026Q@mail.gmail.com>
To: "Mark S. Miller" <erights@google.com>
Cc: David Bruant <david.bruant@labri.fr>, Alex Russell <slightlyoff@google.com>, public-script-coord@w3.org
On Tue, Oct 11, 2011 at 11:54, Mark S. Miller <erights@google.com> wrote:
> Regarding the points I make in the rest of my email, do you know of any that
> make use of configurability for AOP *after* initialization, during the
> normal running of the body of the program?

Yes, these things are done during normal program flow. For example by
changing a value property to a getter and setter pair to support
logging and notifications.

However, I think I am mistaken that existing js libraries depends on
this. I was thinking of dojo.connect and how it used to (I'm not sure
if it still does) replace the function with another function. This
does not require the property to be configurable, writable is enough.

-- 
erik
Received on Tuesday, 11 October 2011 19:14:31 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:04 UTC