views:

87

answers:

3

Do you know how to fix the following issue with math precision?

p RUBY_VERSION # => "1.9.1"
p 0.1%1 # => 0.1
p 1.1%1 # => 0.1
p 90.0%1 # => 0.0
p 90.1%1 # => 0.0999999999999943
p 900.1%1 # => 0.100000000000023

p RUBY_VERSION # => "1.9.2"
p 0.1%1 # => 0.1
p 1.1%1 # => 0.10000000000000009
p 90.0%1 # => 0.0
p 90.1%1 # => 0.09999999999999432
p 900.1%1 # => 0.10000000000002274
+2  A: 

This is true of all computer languages, not just Ruby. It's a feature of representing floating point numbers on binary computers:

What Every Computer Scientist Should Know About Floating Point Arithmetic

duffymo
+1  A: 

Writing 0.1 into a floating point will always result in rounding errors. If you want 'precise' decimal representation, you should use the Decimal type.

xtofl
I haven't noticed such issue in `PHP`. Is there any good reason why Ruby doesn't have "'precise' decimal representation" by default?
Andrey
PHP has the same problem, because it's not about language: http://php.net/manual/en/language.types.float.php
duffymo
+3  A: 

Big Decimal


As the man said;

Squeezing infinitely many real numbers into a finite number of bits requires an approximate representation.


I have however had great success using the BigDecimal class. To quote its intro

Ruby provides built-in support for arbitrary precision integer arithmetic. For example:

42**13 -> 1265437718438866624512

BigDecimal provides similar support for very large or very accurate floating point numbers.


Taking one of your examples;

>> x = BigDecimal.new('900.1')
=> #<BigDecimal:101113be8,'0.9001E3',8(8)>
>> x % 1
=> #<BigDecimal:10110b498,'0.1E0',4(16)>
>> y = x % 1
=> #<BigDecimal:101104760,'0.1E0',4(16)>
>> y.to_s
=> "0.1E0"
>> y.to_f
=> 0.1


As you can see, ensuring decent precision is possible but it requires a little bit of effort.

Chris McCauley
Mind! You're not just adding precision: you're choosing a better representation for decimal numbers. 1/3 will still be rounded.
xtofl
@xtofl - that's a fair point but I hoped that the quote about 'approximate representation' touched on it.
Chris McCauley