Bug Javascript Function parseInt

Not so long ago I encountered a problem with the parseInt JavaScript function. In some cases the parseInt returns an incorrect value. For example, parseInt("08") results in 0 instead of 8 and parseInt("09") also results in 0 instead of 9.
Apparently the reason for this is because the zero in front is trying to tell the browser that this is an octal number, and "08" and "09" are not valid octal numbers.
With parseFloat I didn't have the problem. So to "fix" the problem, I used the following: parseInt(parseFloat("string value"))

Please note that this "bug" only happens when the value being checked is a string and the string starts with a leading zero.

Kevin Dosseray

Comments

Post a Comment

Popular posts from this blog

Scribe and Excel Data Ranges

Another Scribe tip: If you need to import Excel files with Scribe don't forget to give a name to your data range. Otherwise Scribe won't recognize your file. In excel 2003 you can do this as follow: Insert > Name > Define; in excel 2007: Formulas > Define name. Also when you notice that not all of your lines are imported, make sure that your data range is big enough (make sure it includes all of your data lines). Happy Scribing!
Read more

Scribe MVP!

Image
I've been invited to join the Scribe MVP program! And guess what... I've accepted the invitation :-) See here for the complete Scribe MVP list. Scribe MVP... sounds nice, doesn't it? ;-)
Read more