Upgrade Number constructor to ES6.

test/mjsunit/parse-int-float.js

Index: test/mjsunit/parse-int-float.js
diff --git a/test/mjsunit/parse-int-float.js b/test/mjsunit/parse-int-float.js
index 5a9b6f33ccb59aea61ab7e080a8c2abec5b8389e..6befa1db00d7661b66aae7f920a18b066779c1ca 100644
--- a/test/mjsunit/parse-int-float.js
+++ b/test/mjsunit/parse-int-float.js
@@ -114,3 +114,10 @@ assertEquals(state, "throwingString");
 state = null;
 try { parseInt(throwingString, throwingRadix); } catch (e) {}
 assertEquals(state, "throwingString");
+
+// And finally, check that the Harmony additions to the Number
+// constructor is available:
+assertTrue("parseInt" in Number);
+assertTrue("parseFloat" in Number);
+assertEquals(Number.parseFloat('0.1'), parseFloat('0.1'));

[Michael Starzinger, 2014/01/07 16:08:00]

The spec requires "Number.parseFloat" and "parseFloat" to be the same function
object. I think we get that right, but can we add a test in that regard?

// Test that some properties refer to the same function object.
assertSame(Number.parseInt, parseInt);
assertSame(Number.parseFloat, parseFloat);

[sof, 2014/01/07 21:36:29]

Added

+assertEquals(Number.parseInt('0xea'), parseInt('0xEA'));