Fix assertSame for unit testing harness.

Fix assertSame for unit testing harness.

Using isNaN() here is bogus because it performs an implicit toNumber()
conversion, hence something like assertSame(undefined, {}) would not
throw an exception. These are not the NaNs you are looking for.

R=rossberg@chromium.org
TEST=mjsunit

Committed: http://code.google.com/p/v8/source/detail?r=9831

[Michael Starzinger, 2011-10-28 08:26:41]

PTAL.

[rossberg, 2011-10-28 09:05:18]

Aargh!

LGTM

http://codereview.chromium.org/8400056/diff/1/test/mjsunit/mjsunit.js
File test/mjsunit/mjsunit.js (right):

http://codereview.chromium.org/8400056/diff/1/test/mjsunit/mjsunit.js#newcode226
test/mjsunit/mjsunit.js:226: } else if ((expected !== expected) && (found !==
found)) {
Somebody should pull IEEE to court for their NaN semantics.
Somebody should also pull to court the person responsible for the semantics of
isNaN in JavaScript.

http://codereview.chromium.org/8400056/diff/1/test/mjsunit/mjsunit.status
File test/mjsunit/mjsunit.status (right):

http://codereview.chromium.org/8400056/diff/1/test/mjsunit/mjsunit.status#new...
test/mjsunit/mjsunit.status:35: harmony/proxies-function: FAIL
Damn, just when you think that everything is working...