Comment #18 on issue 164 by [email protected]: Wrong order in Object properties interation
http://code.google.com/p/v8/issues/detail?id=164
The right place to have this argument is on the es-discuss list, regarding future versions of EcmaScript. In the ES3.1 (aka ES5) phone calls we all agreed that we should specify a deterministic property iteration order, so that one could count on such an order between browsers. We all agreed that non-indexes should iterate in insertion order on each object, from own object up through inheritance chain. However, given the existing browser behaviors, we could not agree on indexes. We also argued about another iteration determinism issue regards visibility of properties inserted after the iteration began. In the last relevant committee meeting before the spec was set in stone, we agreed on the new "guaranteed not" language. Then, at the last minute, in response to some issues raised on es-discuss, the language unfortunately reverted to "not guaranteed". :(
Since then, some of us (not all) would still like to see future EcmaScript specify a deterministic order and visibility rule. My first choice is the order v8 apparently already does, and for late additions not to be visible. However, I don't much care what we agree on as long as we agree on something deterministic.
Until we have such agreement, I don't see anything wrong in v8's current behavior here. If you'd like to get the browsers to all agree on a behavior you can count on, this is not the right forum.
-- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
