Upgrade Number constructor to ES6.

test/mjsunit/parse-int-float.js

 // Copyright 2008 the V8 project authors. All rights reserved.
 // Redistribution and use in source and binary forms, with or without
 // modification, are permitted provided that the following conditions are
 // met:
 //
 //     * Redistributions of source code must retain the above copyright
 //       notice, this list of conditions and the following disclaimer.
 //     * Redistributions in binary form must reproduce the above
 //       copyright notice, this list of conditions and the following
 //       disclaimer in the documentation and/or other materials provided
@@ skipping 96 matching lines @@
 try { parseInt('123', throwingRadix); } catch (e) {}
 assertEquals(state, "throwingRadix");
 
 state = null;
 try { parseInt(throwingString, 10); } catch (e) {}
 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'));