for-in evaluation order
mikeday at yeslogic.com
Mon Dec 27 03:39:53 PST 2010
Some quick testing with Firefox seems to show that for-in returns
properties in the order they were added to the object, and some scripts
on the web (eg. RaphaelJS) seem to depend on that, unless I'm
horrendously misinterpreting them. This seems... bad?
Are objects implicitly ordered, by implementation convention?
Print XML with Prince!
More information about the es-discuss