query: If the double type can handle the numbers 4.35 and 435, why do 4.35 * 100 evaluates to 434.99999999999994?
positive_passages.docid: 43
positive_passages.text: Is floating point math broken?
negative_passages.docid: 31717
negative_passages.text: Understanding floating point problems
negative_passages.docid: 6352
negative_passages.text: How can I divide two integers to get a double?
negative_passages.docid: 57172
negative_passages.text: Strange result with floating point addition
negative_passages.docid: 3245
negative_passages.text: Double calculation producing odd result
negative_passages.docid: 19232
negative_passages.text: Strange floating-point behaviour in a Java program
negative_passages.docid: 43160
negative_passages.text: How to deal with floating point number precision in JavaScript?
negative_passages.docid: 98294
negative_passages.text: Can decimal numbers be considered "even" or "odd"?
negative_passages.docid: 123022
negative_passages.text: Confusion with floating point numbers
negative_passages.docid: 117210
negative_passages.text: Why is modulus operator not working for double in c#?
negative_passages.docid: 128464
negative_passages.text: How to avoid floating point precision errors with floats or doubles in Java?
negative_passages.docid: 133748
negative_passages.text: Why doesn't Java throw an Exception when dividing by 0.0?
negative_passages.docid: 39535
negative_passages.text: Precision of double after decimal point
negative_passages.docid: 132090
negative_passages.text: Java Double value = 0.01 changes to 0.009999999999999787
negative_passages.docid: 46130
negative_passages.text: "new BigDecimal(13.3D)" results in imprecise "13.3000000000000007105.."?
negative_passages.docid: 157069
negative_passages.text: sum of double precision gives weird results
negative_passages.docid: 106565
negative_passages.text: Why is BigDecimal returning a weird value?