I'm not sure it is such a big issue since the new method would be [[DontEnum]] but I'm willing to let this rest.
The reason why I don't think it is that a big risk is that a lot of people still use Array instead of Object for "associative arrays" and I don't think adding the array extras introduced any problems. Brendan, did you get any bug reports on Spidermonkey when array extras was added? On Wed, Mar 5, 2008 at 17:19, Brendan Eich <[EMAIL PROTECTED]> wrote: > On Mar 5, 2008, at 5:04 PM, Erik Arvidsson wrote: > > > We (Google) find setting the [[DontEnum]] flag with > > propertyIsEnumerable(name, flag) to be quite ugly. I can't find any > > references to why the setter was tagged along onto the getter in this > > way? Is there a reason why we don't want > > setPropertyIsEnumerable(name, flag) instead of overloading the getter? > > Adding any properties to Object.prototype at this point is difficult. > You may break object-detection tests. Is it worth the risk? > > /be > > -- erik _______________________________________________ Es4-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es4-discuss
