Le 29/09/2011 20:10, Brendan Eich a écrit : > On Sep 29, 2011, at 6:54 PM, Geoffrey Sneddon wrote: > >> On 28/09/11 00:06, Waldemar Horwat wrote: >>> Should we standardize __proto__ in Annex B? >>> MarkM + a few others: Yes >>> Waldemar, Doug: No >> Unless we have a definite plan that no ES.Next impl will support __proto__, >> then by all means don't standardize it. > It is a standard (de-facto) What is a de facto standard exactly? The fact that '__proto__' allows to get and set the prototype? This basic definition stands, but I have heard of bugs: https://bugzilla.mozilla.org/show_bug.cgi?id=690027
Firefox 7 recently added a '__proto__' property to Object.prototype (https://bugzilla.mozilla.org/show_bug.cgi?id=690031). Would it be part of the non-mandatory spec? Making __proto__ part of the spec sounds like an incitation to authors to use it. I agree that implementors should agree for interoperability purposes, but I'm not sure the official ECMAScript standard is the right place to do so since it is intended for authors as well. David _______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
