Click here to Skip to main content
Click here to Skip to main content

Wrong usage of Javascript parseInt

, 11 Oct 2013
Rate this:
Please Sign up or sign in to vote.
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,

Editorial Note

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, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

ASP.NET Community

United States United States
The ASP.NET Wiki was started by Scott Hanselman in February of 2008. The idea is that folks spend a lot of time trolling the blogs, googlinglive-searching for answers to common "How To" questions. There's piles of fantastic community-created and MSFT-created content out there, but if it's not found by a search engine and the right combination of keywords, it's often lost.
 
The ASP.NET Wiki articles moved to CodeProject in October 2013 and will live on, loved, protected and updated by the community.
Group type: Collaborative Group

247 members


Comments and Discussions

 
-- There are no messages in this forum --
| Advertise | Privacy | Mobile
Web03 | 2.8.140814.1 | Last Updated 11 Oct 2013
Article Copyright 2013 by ASP.NET Community
Everything else Copyright © CodeProject, 1999-2014
Terms of Service
Layout: fixed | fluid