Differences between version #9424 and #9425

30c30
< Std.parseInt treats inputs that start with 0 as octal.  Accordingly, Std.parseInt("09") will return 0.  This is appropriate according to the ecmascript specification, but is a common source of errors for numeric parsing.  For an overview of the situation, see [[http://stackoverflow.com/questions/2547836/why-doesnt-an-octal-literal-as-a-string-cast-to-a-number|this StackOverFlow response]] All other Haxe targets use native parseInt implementations that parse "09" as 9.
\ No newline at end of file
---
> Std.parseInt treats inputs that start with 0 as octal.  Accordingly, Std.parseInt("09") will return 0.  This is appropriate according to the ecmascript specification, but is a common source of errors for numeric parsing.  For an overview of the situation, see [[http://stackoverflow.com/questions/2547836/why-doesnt-an-octal-literal-as-a-string-cast-to-a-number|this stackoverflow response]] All other Haxe targets use native parseInt implementations that parse "09" as 9.
\ No newline at end of file