for-in evaluation order
mikeday at yeslogic.com
Mon Dec 27 04:25:08 PST 2010
> Note that almost all implementations break for-in enumeration order for dense arrays, for some definition of dense.
This is understandable and very sensible.
> If we try to specify something, implementors will probably object, and each implementation will have specific objections depending on their particular array and object representation.
Ugh. Tempting to randomise the order for non-dense objects, or just beat
developers with the clue-bat until they stop writing code that depends
upon a consistent order :)
Print XML with Prince!
More information about the es-discuss