In JavaScript, why does zero divided by zero return NaN, but any other divided by zero return Infinity?

javascript math floating-point nan infinity
Bloodyaugust picture Bloodyaugust · Sep 17, 2013 · Viewed 28.9k times · Source

It seems to me that the code

console.log(1 / 0)

should return NaN, but instead it returns Infinity. However this code:

console.log(0 / 0)

does return NaN. Can someone help me to understand the reasoning for this functionality? Not only does it seem to be inconsistent, it also seems to be wrong, in the case of x / 0 where x !== 0

Answer

Oliver Charlesworth picture Oliver Charlesworth · Sep 17, 2013

Because that's how floating-point is defined (more generally than just Javascript). See for example:

Crudely speaking, you could think of 1/0 as the limit of 1/x as x tends to zero (from the right). And 0/0 has no reasonable interpretation at all, hence NaN.

Related questions

Float sum with javascript

Possible Duplicate: Is JavaScript's Math broken? I'm calculating the sum of several float values using javascript and... I've noticed a strange thing never seen before. Executing this code: parseFloat('2.3') + parseFloat('2.4') I obtain 4.699999999999999 So... what sould I …

Read More
JavaScript: Round to a number of decimal places, but strip extra zeros

Here's the scenario: I'm getting .9999999999999999 when I should be getting 1.0. I can afford to lose a decimal place of precision, so I'm using .toFixed(15), which kind of works. The rounding works, but the problem is that I'm given 1.000000000000000. Is there …

Read More
Why does adding two decimals in Javascript produce a wrong result?

Possible Duplicate: Is JavaScript’s Math broken? Why does JS screw up this simple math? console.log(.1 + .2) // 0.3000000000000004 console.log(.3 + .6) // 0.8999999999999999 The first example is greater than the correct result, while the second is less. ???!! How do you fix this? Do you …

Read More