Comment #27 on issue 883 by nulldevice.eu: for in loops don't occur in
defined order
http://code.google.com/p/chromium/issues/detail?id=883
Especially I love the comment in PropertyMapHashTable.h of SquirrelFish:
// lastIndexUsed is an ever-increasing index used to identify the order
items
// were inserted into the property map. It's required that
getEnumerablePropertyNames
// return the properties in the order they were added for compatibility
with other
// browsers' JavaScript implementations.
So, V8 is fast and lean b/c you guys want to reorder object properties in
order to reduce cache size and
increase hit rate, right? And SquirrelFish is not fast and lean according
to this logic? And yes, MS did prefer
UTF16, b/c they were not able to write a fast sort function for UTF8. Crap.
As Google does not seem to have the resources for further investigation, I
will invest my time to do it, even
after I came home at 6 am this morning and today is Sunday^^
Attachments:
PropertyMapHashTable.h 3.0 KB
--
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
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
