Test diff output shouldn't depend on object property order

[gijsk]

If one uses deepEqual to compare two objects and the equality test fails, the diff output seems to depend on the order in which properties were set on the object (probably because it uses for...in). I made a trivial example using jsfiddle

I haven't quite figured out how to trick it into behaving its worst, but I've definitely seen it produce rather terrible output when property order doesn't match across objects. For more easily figuring out 'where' in the object differences occur, it would be nice if the output were improved (perhaps by sorting the properties of each object before doing a diff?).

[jzaefferer]

A little edgy casy, isn't it? Would you be interested in helping to patch that? You know, pull request and such.

[gijsk]

Definitely interested. I haven't checked how hard it is to fix this yet, at work, crunch time, yada yada. Will give it a shot when I'm on my commute home.

[gijsk]

Done, see issue #208. I suck too much at github to get the pull request for multiple commits to show up in this issue. Not sure if you want to close this one in favour of #208, so leaving it open for now.