Click here to Skip to main content
65,938 articles
CodeProject is changing. Read more.
Articles
(untagged)

Wrong usage of Javascript parseInt

0.00/5 (No votes)
9 Jul 2012 1  
I have seen most of the developers using parseInt to convert a string to a number. Here we need to understand that What does this parseInt will do,

This articles was originally at wiki.asp.net but has now been given a new home on CodeProject. Editing rights for this article has been set at Bronze or above, so please go in and edit and update this article to keep it fresh and relevant.

I have seen most of the developers using parseInt to convert a string to a number. Here we need to understand that What does this parseInt will do, what all parameters it accepts.

ParseInt will behave differently depending upon the parameters given.

for example ::

parseInt("10")  ---> Result ::  10

parseInt("9")  ---> Result ::  9

parseInt("109") ---> Result ::  109

Have you ever tried giving  "08" or "09", it will give "0" as result. I have seen in most of the javascript calendar controls using parseInt where the number passed to it will be in two digit format. So when the date contains 09 0r 08, all calculations will go wrong.

The above scenario is just a simple example of making mistakes. Lot of people will do this kind of mistakes without understanding the actual purpose of available functions and properties.

So whenever you go for parseInt for integer conversion, please do practice the below snippet ::

parseInt("08",10)  ---> Result :: 8

parseInt("09",10)  ---> Result :: 9

parseInt("018",10)  ---> Result :: 18


For more info

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here