Comments on: Javascript parseInt() quirk http://www.chapter31.com/2006/09/28/javascript-parseint-quirk/ Rich Internet Application development Tue, 31 Jan 2012 15:10:27 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Carl Sharman http://www.chapter31.com/2006/09/28/javascript-parseint-quirk/comment-page-1/#comment-119942 Carl Sharman Thu, 16 Sep 2010 11:50:06 +0000 http://www.chapter31.com/2006/09/28/javascript-parseint-quirk/#comment-119942 Nice one, just ran into the same issue, thanks for sharing this. Go Sharmans :) Nice one, just ran into the same issue, thanks for sharing this. Go Sharmans :)

]]> By: JS http://www.chapter31.com/2006/09/28/javascript-parseint-quirk/comment-page-1/#comment-118969 JS Fri, 13 Aug 2010 11:36:24 +0000 http://www.chapter31.com/2006/09/28/javascript-parseint-quirk/#comment-118969 Hi, I noticed this quirk too! Say if your date field is "01/07/2010" you get "07" for your month field which needs converting to int 7. If you do ("07"*1) you will get a value 7. JavaScript sees the * sign as an integer function so converts the string to an integer for you. What I noticed: "07"+1 == "071" // you can't do this as it converts to string '+' is overloaded "07"*1 == 7 // ok "07"-1 == 6 // ok Is this better/faster than your method? Hi,
I noticed this quirk too! Say if your date field is “01/07/2010″ you get “07″ for your month field which needs converting to int 7. If you do (“07″*1) you will get a value 7. JavaScript sees the * sign as an integer function so converts the string to an integer for you.

What I noticed:
“07″+1 == “071″ // you can’t do this as it converts to string ‘+’ is overloaded
“07″*1 == 7 // ok
“07″-1 == 6 // ok

Is this better/faster than your method?

]]> By: Sean http://www.chapter31.com/2006/09/28/javascript-parseint-quirk/comment-page-1/#comment-21798 Sean Wed, 26 Sep 2007 17:53:16 +0000 http://www.chapter31.com/2006/09/28/javascript-parseint-quirk/#comment-21798 Thanks for this. I spent half the day trouble shooting this very issue. Thanks for this. I spent half the day trouble shooting this very issue.

]]>