A friend showed me that (at least, in the google chrome console) the following statement prints true:

1/Math.pow(0.9999999999999999, Number.MAX_SAFE_INTEGER) === Math.E

And indeed, 1/Math.pow(0.9999999999999999, Number.MAX_SAFE_INTEGER) is 2.718281828459045.

This can't be a coincidence?!

Could someone explain what is going on behind the scenes to make this work?

According to wolfram alpha, the correct value should be approximately 1/0.40628 which is approximately 2.4613566998129373 -- very far off from Math.E. (I am assuming that wolframalpha is more precise in its calculations than javascript, but I may be wrong).

Any explanation would be appreciated.

Bonus: What is the true approximate mathematical value of that expression, I wonder? I found this:

n = 0.0000000000000001
(1 - n)^MAX_INT =  1 + (MAX_INT choose 2) * n + (MAX_INT choose 3) * n^2 + ... + n^MAX_INT 

but I have no idea how to approximate that.

I tested the above expression in wolfram alpha and got 2.46 as well.

A friend showed me that (at least, in the google chrome console) the following statement prints true:

1/Math.pow(0.9999999999999999, Number.MAX_SAFE_INTEGER) === Math.E

And indeed, 1/Math.pow(0.9999999999999999, Number.MAX_SAFE_INTEGER) is 2.718281828459045.

This can't be a coincidence?!

Could someone explain what is going on behind the scenes to make this work?

According to wolfram alpha, the correct value should be approximately 1/0.40628 which is approximately 2.4613566998129373 -- very far off from Math.E. (I am assuming that wolframalpha is more precise in its calculations than javascript, but I may be wrong).

Any explanation would be appreciated.

Bonus: What is the true approximate mathematical value of that expression, I wonder? I found this:

n = 0.0000000000000001
(1 - n)^MAX_INT =  1 + (MAX_INT choose 2) * n + (MAX_INT choose 3) * n^2 + ... + n^MAX_INT 

but I have no idea how to approximate that.

I tested the above expression in wolfram alpha and got 2.46 as well.

• javascript
• floating-point

• According to wolfram alpha it is the same. – Roger Far Commented Dec 14, 2014 at 18:05
• @Rogier21 What do you mean it's the same? wolframalpha./input/… – soktinpk Commented Dec 14, 2014 at 18:09
• euler's number is in WA 2.718 but of you check the link above it will give the same answer as Javascript. e == 0.99^maxint = true, while the decimal values are no equal. So both JS and WA do give the same answers. – Roger Far Commented Dec 14, 2014 at 18:13
• 1 @Rogier21 I don't think that's valid since even wolframalpha./input/… that link returns true. Wolfram alpha has gone crazy! (e == e + 1?) – soktinpk Commented Dec 14, 2014 at 18:14
• Confirmed Node.js gets the same if you define Number.MAX_SAFE_INTEGER. Numbers above 0.9999... are rounded to 1, so that's basically (1 - epsilon) where epsilon is the smallest unit the number can represent at that scale. This probably has something to do with how the power converges to e, but not sure how. – rich remer Commented Dec 14, 2014 at 18:15

2 Answers 2

pow(x, y) is typically puted as exp(log(x) * y), so let's start there.

We have:

• x = 0.9999999999999999, which rounds to x = 1 - eps (where eps == 2^-53).
• y = 2^53 - 1 i.e. y = 1 / eps (approximately).

So we're actually calculating exp(log(1 - eps) * 1/eps).

The Taylor series expansion of log(1 - k) is -k - k^2/2 - ..., but in our case all the higher-order terms will be truncated.

So we have exp(-eps / eps), or exp(-1), which is 1 / e.

1 - 0.9999999999999999                  //  1.1102230246251565e-16
Math.log(1 - 1.1102230246251565e-16)    // -1.1102230246251565e-16
1 / Number.MAX_SAFE_INTEGER             //  1.1102230246251568e-16