Gmosx's Blog: Nasty JavaScript catch

Wednesday, July 8, 2009

JavaScript definitely has some rough edges. Consider this:

parseInt("07") // => 7

parseInt("08") // => NaN

This is a great reason for a 20 minutes long debugging session :(

dionyzizAug 25, 2009 03:12 AM
Starting a numeric string with a zero marks it as being in oct format?
ReplyDelete
StickupkidSep 2, 2009 02:26 AM
You should always supply a base number as the second argument when using parseInt() - base 10 in this instance. You can never rely on it being accurate 100% of the time especially if the user can input the string.
ReplyDelete