Why does division by zero in IEEE754 standard results in Infinite value?

by

It’s a nonsense from the mathematical perspective.

Yes. No. Sort of.

The thing is: Floating-point numbers are approximations. You want to use a wide range of exponents and a limited number of digits and get results which are not completely wrong. 🙂

The idea behind IEEE-754 is that every operation could trigger “traps” which indicate possible problems. They are

  • Illegal (senseless operation like sqrt of negative number)
  • Overflow (too big)
  • Underflow (too small)
  • Division by zero (The thing you do not like)
  • Inexact (This operation may give you wrong results because you are losing precision)

Now many people like scientists and engineers do not want to be bothered with writing trap routines. So Kahan, the inventor of IEEE-754, decided that every operation should also return a sensible default value if no trap routines exist.

They are

  • NaN for illegal values
  • signed infinities for Overflow
  • signed zeroes for Underflow
  • NaN for indeterminate results (0/0) and infinities for (x/0 x != 0)
  • normal operation result for Inexact

The thing is that in 99% of all cases zeroes are caused by underflow and therefore in 99%
of all times Infinity is “correct” even if wrong from a mathematical perspective.

More Related Contents:

  1. How should I do floating point comparison?
  2. Why is NaN not equal to NaN? [duplicate]
  3. Algorithm to convert an IEEE 754 double to a string?
  4. How do I display the binary representation of a float or double?
  5. Should we compare floating point numbers for equality against a *relative* error?
  6. Large numbers erroneously rounded in JavaScript
  7. What is the difference between concurrency and parallelism?
  8. Why shouldn’t I use “Hungarian Notation”?
  9. Expression Versus Statement
  10. Prefer composition over inheritance?
  11. Singletons: good design or a crutch? [closed]
  12. Python float – str – float weirdness
  13. Test loops at the top or bottom? (while vs. do while) [closed]
  14. How do I assess the hash collision probability?
  15. When to use unsigned values over signed ones?
  16. Making a system call that returns the stdout output as a string
  17. Allen Holub wrote “You should never use get/set functions”, is he correct? [duplicate]
  18. What are the lesser known but useful data structures?
  19. Why is it recommended to have empty line in the end of a source file?
  20. Are exceptions really for exceptional errors? [closed]
  21. Ranges of floating point datatype in C?
  22. Generate colors between red and green for a power meter?
  23. Calculating a 2D Vector’s Cross Product
  24. Why does floating-point arithmetic not give exact results when adding decimal fractions?
  25. Hash Code and Checksum – what’s the difference?
  26. When should a method be static?
  27. What precisely does the %g printf specifier mean?
  28. Why are leading zeroes used to represent octal numbers?
  29. Maximum number of decimal digits that can affect a double
  30. Converting Int to Float or Float to Int using Bitwise operations (software floating point)

Leave a Comment