Allen Wirfs-Brock (2014-10-03T15:13:00.000Z)
domenic at domenicdenicola.com (2014-10-15T18:35:31.458Z)
On Oct 3, 2014, at 7:35 AM, Rick Waldron wrote: > The security concern was for validating user input and any reliance on the existing semantics being broken. parseInt: "parseInt may interpret only a leading portion of string as an integer value; it ignores any code units that cannot be interpreted as part of the notation of an integer, and no indication is given that any such code units were ignored." - ES5: `parseInt("0b10") //0` - ES6 as specified: `parseInt("0b10") //0` - ES6 if new forms recognized: `parseInt("0b10") //2` Number: "ToNumber applied to Strings applies the following grammar to the input String interpreted as a sequence of UTF-16 encoded code points. If the grammar cannot interpret the String as an expansion of StringNumericLiteral, then the result of ToNumber is NaN." - ES5: `Number("0b10") //NaN` - ES6: `Number("0b10") //2`