Is checking a double for equality ever safe?

by

The reason you shouldn’t check floats for equality is that floating point numbers are not perfectly precise — there’s some inaccuracy in storage with some numbers, such as those that extended too far into the mantissa and repeating decimals (note that I’m talking about repeating decimals in base 2). You can think of this imprecision as “rounding down”. The digits that extend beyond the precision of the floating-point number are truncated, effectively rounding down.

If it has not changed, it will keep that equality. However, if you change it even slightly, you probably should not use equalities, but instead a range like (x < 0.0001 && x > -.0001).

In short: as long as you’re not playing with x at a very small level, it’s OK.

It is safe if the 0 you’re trying to catch is the original 0 set at initialization. However, it isn’t safe if you’re expecting a 0 from a mathematical operation.

More Related Contents:

  1. Division of integers in Java [duplicate]
  2. Retain precision with double in Java
  3. Double vs. BigDecimal?
  4. Why does the division of two integers return 0.0 in Java? [duplicate]
  5. Convert float to double without losing precision
  6. Why does Math.round(0.49999999999999994) return 1?
  7. How can a primitive float value be -0.0? What does that mean?
  8. Why does Double.NaN==Double.NaN return false?
  9. comparing float/double values using == operator
  10. Manipulating and comparing floating points in java
  11. What is the difference between the float and integer data type when the size is the same?
  12. why f is placed after float values?
  13. Why converting from float to double changes the value?
  14. Java floating point high precision library [closed]
  15. How can I handle precision error with float in Java?
  16. Why does this subtraction not equal zero?
  17. Why does changing the sum order returns a different result?
  18. What do F and D mean at the end of numeric literals?
  19. What is the inclusive range of float and double in Java?
  20. Why does adding 0.1 multiple times remain lossless?
  21. How do I check if a zero is positive or negative?
  22. Java double precision sum trouble
  23. Loss of precision – int -> float or double
  24. Why can’t we use ‘==’ to compare two float or double numbers [duplicate]
  25. Why do floating-point numbers have signed zeros?
  26. Are the bit patterns of NaNs really hardware-dependent?
  27. How to convert IEEE-11073 16-bit SFLOAT to simple float in Java?
  28. Java: Inaccuracy using double [duplicate]
  29. Java double comparison epsilon
  30. What is float in Java?

Leave a Comment