My favorites | Sign in
v8
Project Home Downloads Wiki Issues Source Code Search
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 344: Enumeration order does not match WebKit nightlies
1 person starred this issue and may be notified of changes. Back to list
Status:  Duplicate
Owner:  ----
Closed:  May 2009
Cc:  ager@chromium.org


Sign in to add a comment
 
May 14, 2009
Project Member #1 ager@chromium.org
In your example, there are properties with integer names.  V8 has never enumerated 
these elements in insertion order.  Elements are enumerated in numerical order.  For 
your example, the only change after r1722 is that the elements are enumerated first 
instead of last (to match the JSC behavior for arrays).

Chrome 1.0.154.65:
two,four,six,  (named properties in insertion order)
one,seven,three,five,  (integer named properties in numerical order)

ToT:
one,seven,three,five,   (integer named properties in numerical order)
two,four,six,   (named properties in insertion order)

If it is worse to enumerate the elements first I can change that, but I don't think 
r1722 made anything worse than it was before?

Status: PendingFurtherInfo
Cc: a...@chromium.org
May 15, 2009
#2 o...@chromium.org
Ah. I had misunderstood the change. This still seems like a bug though since we don't
match other browsers here.
May 15, 2009
Project Member #3 ager@chromium.org
(No comment was entered for this change.)
Status: Duplicate
Mergedinto: 12
May 15, 2009
Project Member #4 ager@chromium.org
(No comment was entered for this change.)
Mergedinto: 164
Sign in to add a comment

Powered by Google Project Hosting