Why Does `parseInt` Sometimes Give Unexpected Results with Leading Zeros?

Working Around JavaScript's Perplexing ParsInt Octal Behavior

JavaScript's parseInt function occasionally behaves unexpectedly, especially when dealing with leading zeros. Specifically, numbers with leading zeros are misinterpreted as octal integers, resulting in erroneous outputs. This issue stems from the parseInt function's assumption that a leading zero denotes an octal number. As octal numbers exclude 8 and 9, values starting with these digits are misinterpreted as zeroes.

Overcoming the Octal Snag

Fortunately, there are several strategies to circumvent this peculiar behavior:

1. Explicit Base Specification:

By explicitly defining the base or radix, we can ensure that parseInt interprets the input as a decimal number. For instance:

parseInt('08', 10); // 8

2. Number Method:

Another option is to employ the Number method, which automatically interprets the input as a decimal number:

Number('08'); // 8

Note:

The ES5 standard introduced a modification that eliminates this puzzling octal behavior. However, this change is browser-dependent. Please consult the Mozilla documentation for further details.

The above is the detailed content of Why Does `parseInt` Sometimes Give Unexpected Results with Leading Zeros?. For more information, please follow other related articles on the PHP Chinese website!