Re: My ECMAScript 7 wishlist

2014-09-25 Thread Tab Atkins Jr.
On Wed, Sep 24, 2014 at 3:28 PM, Brendan Eich bren...@mozilla.org wrote: Tab Atkins Jr. wrote: Using subclassing to bung in some arbitrary trait is really terrible. :/ It requires either adding it up high in your class hierarchy, or having to write a custom NoSuchPropertyClass which extends

Re: My ECMAScript 7 wishlist

2014-09-25 Thread Tab Atkins Jr.
On Thu, Sep 25, 2014 at 12:50 PM, Brendan Eich bren...@mozilla.org wrote: Tab Atkins Jr. wrote: If you try to add it in a targeted way in the middle of your hierarchy, it requires either __proto__ hacking, something like: class superclass {...} ... x = makeNSPProxy() x.__proto__ =

Re: My ECMAScript 7 wishlist

2014-09-25 Thread Boris Zbarsky
On 9/25/14, 4:31 PM, Tab Atkins Jr. wrote: Yes, that is what I'm proposing. If lookup fails completely (reaches Object.prototype without finding the named property), it then does a second lookup for the magic NSP property, and if it finds it, executes it with the property name, returning the

Re: My ECMAScript 7 wishlist

2014-09-25 Thread Brendan Eich
On Sep 25, 2014, at 7:56 PM, Boris Zbarsky bzbar...@mit.edu wrote: SpiderMonkey used to support __noSuchMethod__, I believe. I implemented __noSuchMethod__ long ago, for the TIBET folks (Smalltalk style JS framework; they wanted a doesNotUnderstand analogue). Please note well the difference