Home / ASP.NET Wiki / Javascript / Wrong usage of Javascript parseInt

Wrong usage of Javascript parseInt

 Rate It (4)

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

Revision number 3, Monday, July 09, 2012 6:53:43 PM by codeNickel

Comments

Hello, If I may add, that happens because when you prefix a number with 0, browser takes it as a Octal number. 08 and 09 are not valid octal number so parseInt outputs 0. So we exceptionally have to tell that the value being parsed must use decimal base.

Shortcuts

Table of Contents

Top Wiki Contributors

(last 30 days)

  1. francissvk (1)
  2. deepeshsp (1)