Comment #12 on issue 883 by jeresig: for in loops don't occur in defined order http://code.google.com/p/chromium/issues/detail?id=883
@stav.roy: The specification does not define how an implementation should handle it - therefore an implementation should conform with other implementations. Considering that every single other popular ECMAScript implementation implements the same property looping type it becomes that much more important to try and get it right. I'm sure you get pissed when Internet Explorer goes off and does something different from every other browser (especially when it causes a regression to occur) - the same should be happening here. The argument that they're doing it to "keep the engine fast and lean" is bogus. There are two other, faster, ECMAScript engines out there: SquirrelFish and TraceMonkey and they both implement the looping indentically. I just want to emphasize the point: This change makes V8 work differently from every other major ECMAScript implementation and causes actual, real world, code to break. There is no reason why this shouldn't be fixed. -- 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
