Skip to main content

parseInt() galore

After the Falsy post, here is another interesting table listing various values as evaluated by parseInt(). Some are quirky indeed :)

Free lunch to anyone who shows me another table that covers parseInt() in such detail :P

ExpressionValueRemarks
parseInt("23")23
parseInt(" 23")23Leading white space is dropped
parseInt("-23")-23
parseInt(23)23
parseInt(023)19Radix 8 is used
parseInt(0x23)35Radix 16 is used
parseInt("23",4)11Radix 4 is used
parseInt("23",4.99)11Radix is always converted to int32
parseInt("23",36)75Radix 36 is used
parseInt("z",36)35Radix 36 is used
parseInt("23",37)NaNMax Radix is 36
parseInt("23",1)NaNMin Radix is 2
parseInt("23",0)23Radix used is 10
parseInt("23",-1)NaNMin Radix is 2
parseInt("23",3)2Radix 3 can use only 0,1,2
parseInt("023")19Radix defaults to 8
parseInt("0x23")35Radix defaults to 16
parseInt("023",5)13Radix used is 5
parseInt("0x23",5)0Radix used is 5
parseInt(023,5)1023 is a base 8 number, i.e. 19
parseInt(0x23,5)30x23 is a base 16 number, i.e. 35
parseInt(1e2)1001e2 is computed first
parseInt("1e2")1e is not a valid digit
parseInt("1e2",15)4371e2 is a valid base 15 number
parseInt("")NaN
parseInt()NaN
parseInt(null)NaN
parseInt(NaN)NaN
parseInt(undefined)NaN
parseInt(true)NaN
parseInt(false)NaN
parseInt("x23")NaN
parseInt("1234567890123456")1234567890123456
parseInt("12345678901234567")12345678901234568Approximation after 16 digits
parseInt("123456789012345678")1234567890123456800 is replaced after 17 digits
parseInt("123456789012345678901")123456789012345680000
parseInt("1234567890123456789012")1.2345678901234568e+21We go exponential now

Comments

  1. had used ParseInt many times in the code never thought about so many permutations.. :) good ri

    ReplyDelete
  2. Thanks Pinaki.
    Thanks Pavanesh, so you finally read my blog :p

    ReplyDelete
  3. Good post for the developers..:)

    Amar

    ReplyDelete

Post a Comment

Popular posts from this blog

Using duplicate IDs in HTML

Well today I'm being a bit controversial. Let us see what the HTML5 spec says about unique IDs in a HTML file. The  id  attribute specifies its element's  unique identifier (ID) . The value must be unique amongst all the IDs in the element's  home subtree  and must contain at least one character. The value must not contain any  space characters . An element's  unique identifier  can be used for a variety of purposes, most notably as a way to link to specific parts of a document using fragment identifiers, as a way to target an element when scripting, and as a way to style a specific element from CSS. Yes its been mentioned almost everywhere on the planet that ID must be unique. Now let us look at the below code, Launch dup.css #p2 {   background-color: yellow;  } dup-id.html <!DOCTYPE html> <html>   <head>     <title>Duplicate ID Tester</title> <link rel="stylesheet" href="dup.css" />  

Minimal required code in HTML5

I've encountered this question repeatedly of late. "What are the tags required at bare minimum for a html file?" Earlier there were a bunch of mandatory tags that were required for any html file. At bare minimum, the recommended structure was: (ref: http://www.w3.org/TR/html4/struct/global.html ) <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <HTML>   <HEAD>     <TITLE>A small HTML</TITLE>   </HEAD>   <BODY>     <P>Small HTML file!</P>   </BODY> </HTML> Yes, using capitals for the tags was the way to go! Those were the days of the purists and strict was the way to be. Now open your notepad and copy the above code, save the file as old.html and launch it in Chrome or Firefox. You will see only one line "Small HTML file!" shown. Now launch the developer tools in Chrome or Inspect Element in Firefox. Thi

Fixing Date, Time and Zone on RHEL 6 command line

Had to fix all time related issues on a remote RHEL 6 server which runs without any windowing system. Plain ol' command line. Documenting steps here for future reference: Check to see if your date and timezone settings are accurate: # date # cat /etc/sysconfig/clock The server I accessed had wrong settings for both the commands. Here are the steps I used to correct: Find out your timezone from the folder /usr/share/zoneinfo # ls /usr/share/zoneinfo Mine was pointing to America/EDT instead of  Asia/Calcutta Update and save the /etc/sysconfig/clock file to # sudo vi /etc/sysconfig/clock ZONE="Asia/Calcutta" UTC=true ARC=false Remove the /etc/localtime # sudo rm /etc/localtime Create a new soft link to your time zone # cd /etc # sudo ln -s /usr/share/zoneinfo/Asia/Calcutta /etc/localtime # ls -al localtime Now it should show the link to your time zone Set your hardware clock to UTC # sudo hwclock --systohc --utc # hwclock --show Update your t