Why is floating point arithmetic in C# imprecise?

by

Floating point only has so many digits of precision. If you’re seeing f1 == f2, it is because any difference requires more precision than a 32-bit float can represent.

I recommend reading What Every Computer Scientist Should Read About Floating Point

More Related Contents:

  1. Double to string conversion without scientific notation
  2. When should I use double instead of decimal?
  3. Is floating-point math consistent in C#? Can it be?
  4. Floating point comparison functions for C#
  5. How To Represent 0.1 In Floating Point Arithmetic And Decimal
  6. C# Float expression: strange behavior when casting the result float to int
  7. Coercing floating-point to be deterministic in .NET?
  8. How to calculate float type precision and does it make sense?
  9. Formatting a float to 2 decimal places
  10. Formatting doubles for output in C#
  11. Casting a result to float in method returning float changes result
  12. How to convert a Decimal to a Double in C#?
  13. Is it safe to check floating point values for equality to 0?
  14. Understanding floating point problems
  15. C#: Convert Byte array into a float
  16. Convert from scientific notation string to float in C#
  17. Float/double precision in debug/release modes
  18. Best way to parse float?
  19. How can I test for negative zero?
  20. Efficient way to round double precision numbers to a lower precision given in number of bits
  21. Why does a float variable stop incrementing at 16777216 in C#?
  22. How to convert Decimal to Double in C#?
  23. Why is the “f” required when declaring floats?
  24. Converting String To Float in C#
  25. Comparing floating point values
  26. Is floating point arithmetic stable? [duplicate]
  27. Rule of thumb to test the equality of two doubles in C#?
  28. What’s the best way to represent System.Decimal in Protocol Buffers?
  29. How to get floats value without including exponential notation
  30. Why does “dtoa.c” contain so much code?

Leave a Comment