query: Strange floating-point behaviour in a Java program
positive_passages.docid: 43
positive_passages.text: Is floating point math broken?
negative_passages.docid: 94897
negative_passages.text: ruby: converting from float to integer in ruby produces strange results
negative_passages.docid: 39093
negative_passages.text: How to manually parse a floating point number from a string
negative_passages.docid: 114832
negative_passages.text: Why does this floating-point calculation give different results on different machines?
negative_passages.docid: 60193
negative_passages.text: How to cast a double to an int in Java by rounding it down?
negative_passages.docid: 35622
negative_passages.text: Is floating-point == ever OK?
negative_passages.docid: 7533
negative_passages.text: Why do floating-point numbers have signed zeros?
negative_passages.docid: 81719
negative_passages.text: Very different results from evaluating same expression with different precisions
negative_passages.docid: 31717
negative_passages.text: Understanding floating point problems
negative_passages.docid: 34746
negative_passages.text: Retain precision with double in Java
negative_passages.docid: 128038
negative_passages.text: How to cancel floating point factors?
negative_passages.docid: 47542
negative_passages.text: How come this is happening in java?
negative_passages.docid: 70350
negative_passages.text: Python rounding error with float numbers
negative_passages.docid: 57172
negative_passages.text: Strange result with floating point addition
negative_passages.docid: 71966
negative_passages.text: Floating point vs integer calculations on modern hardware
negative_passages.docid: 79481
negative_passages.text: Why double.Parse("0.05") returns 5.0?
negative_passages.docid: 113466
negative_passages.text: ArithmeticException: "Non-terminating decimal expansion; no exact representable decimal result"