Javascript, why treated as octal

Posted on

Javascript, why treated as octal – Even if we have a good project plan and a logical concept, we will spend the majority of our time correcting errors abaout javascript and javascript. Furthermore, our application can run without obvious errors with JavaScript, we must use various ways to ensure that everything is operating properly. In general, there are two types of errors that you’ll encounter while doing something wrong in code: Syntax Errors and Logic Errors. To make bug fixing easier, every JavaScript error is captured with a full stack trace and the specific line of source code marked. To assist you in resolving the JavaScript error, look at the discuss below to fix problem about Javascript, why treated as octal.

Problem :

I’m passing as parameter an id to a javascript function, because it comes from UI, it’s left zero padded. but it seems to have (maybe) “strange” behaviour?

    console.log(0000020948);  //20948
    console.log(0000022115);   //9293 which is 22115's octal 
    console.log(parseInt(0000022115, 10));  // 9293 which is 22115's octal
    console.log(0000033959);  //33959
    console.log(20948);  //20948
    console.log(22115); //22115
    console.log(33959); //33959

how can I make sure they are parsing to right numebr they are? (decimal)


just make it clearer:

those numbers come from the server and are zero padded strings. and I’m making a delete button for each one.


function printDelButton(value){
          console.log(typeof value);  //output string 
  return '<a href="#" onclick="deleteme('+value+')"><img src="images/del.png"></a>'


function printDelButton(value){
console.log(typeof value); //output numeric
    console.log(value);   //here output as octal .... :S

I tried :

console.log(parseInt(0000022115, 10));  // 9293 which is 22115's octal

and still parsing as Octal

Solution :

If you receive your parameters as string objects, it should work to use

 parseInt(string, 10)

to interpret strings as decimal, even if they are beginning with 0.

In your test, you pass the parseInt method a number, not a string, maybe that’s why it doesn’t return the expected result.


 parseInt('0000022115', 10)

instead of

parseInt(0000022115, 10)

that does return 221115 for me.

If you start it with a 0, it’s interpreted as an Octal number.


Note the article’s warning here:

You should never precede a number with a zero unless you are
specifically looking for an octal conversion!

Consider looking here for ideas on removing the leadings 0s:
Truncate leading zeros of a string in Javascript

Leading 0s indicate that the number is octal.

parseInt parses a string containing a number.
parseInt(0000022115, 10) passes a numeric literal. The literal is parsed in octal by the JS interpreter, so you’re passing a raw numeric value to parseInt.

Unless you can intercept a string version of this number, you’re out of luck.

That being said, if you can get a string version of your octal (calling toString() won’t help), this will work:

parseInt(variable_string.replace(/^0+/, ''), 10);



That should give you just the numbers stripping the zeros (if you have to support decimals, you’ll need to edit to account for the ‘.’, and of course ‘,’ is fun too… and I really hope you don’t have to handle all the crazy different ways Europeans write numbers! )

If number came from server as zero padded string then use +"0000022115"


if (021 < 019) console.log('Paradox');

JS treat zero padded numbers like octal only if they are valid octal – if not then it treat it as decimal. To not allow paradox 'use strict' mode

Leave a Reply

Your email address will not be published. Required fields are marked *