Comments on: Ruby thinks (19.99 * 100).to_i = 1998 http://www.mokisystems.com/blog/ruby-thinks-1999-100to_i-1998/ Addressing such topics as: web programming, design, ruby on rails, cake php, postgresql, linux, seo Sat, 12 Nov 2011 05:39:30 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: Wes Bangerter http://www.mokisystems.com/blog/ruby-thinks-1999-100to_i-1998/comment-page-1/#comment-493 Wes Bangerter Tue, 19 May 2009 20:47:28 +0000 http://www.mokisystems.com/blog/?p=60#comment-493 Just to verify what Marnen wrote, using a BigDecimal works with the example Daniel posted. >> require 'bigdecimal' >> (BigDecimal.new('19.99') * 100).to_i => 1999 Just to verify what Marnen wrote, using a BigDecimal works with the example Daniel posted.

>> require ‘bigdecimal’
>> (BigDecimal.new(’19.99′) * 100).to_i
=> 1999

]]> By: Marnen Laibow-Koser http://www.mokisystems.com/blog/ruby-thinks-1999-100to_i-1998/comment-page-1/#comment-491 Marnen Laibow-Koser Sun, 17 May 2009 03:28:05 +0000 http://www.mokisystems.com/blog/?p=60#comment-491 Wes: I'm not surprised that this is an IEEE float issue. Leo: Wrong conclusion. The right conclusion: don't use *IEEE floats* to do math. Ruby has a BigDecimal library that completely gets around this problem by not using IEEE floats. Use it for math. Wes: I’m not surprised that this is an IEEE float issue.

Leo: Wrong conclusion. The right conclusion: don’t use *IEEE floats* to do math. Ruby has a BigDecimal library that completely gets around this problem by not using IEEE floats. Use it for math.

]]> By: Wes Bangerter http://www.mokisystems.com/blog/ruby-thinks-1999-100to_i-1998/comment-page-1/#comment-478 Wes Bangerter Wed, 15 Apr 2009 23:27:06 +0000 http://www.mokisystems.com/blog/?p=60#comment-478 "This behavior is not specific to Ruby. The reason Ruby behaves like this is that it adheres to the IEEE standard for floating point numbers, which is common to most programming languages." From http://www.ruby-forum.com/topic/178503 You can read more about it at: http://en.wikipedia.org/wiki/Floating_point#Accuracy_problems Or a lot more about it at: http://docs.sun.com/source/806-3568/ncg_goldberg.html “This behavior is not specific to Ruby. The reason Ruby behaves like this is that it adheres
to the IEEE standard for floating point numbers, which is common to most programming languages.”
From http://www.ruby-forum.com/topic/178503

You can read more about it at:
http://en.wikipedia.org/wiki/Floating_point#Accuracy_problems

Or a lot more about it at:
http://docs.sun.com/source/806-3568/ncg_goldberg.html

]]> By: Leo http://www.mokisystems.com/blog/ruby-thinks-1999-100to_i-1998/comment-page-1/#comment-475 Leo Mon, 06 Apr 2009 20:18:06 +0000 http://www.mokisystems.com/blog/?p=60#comment-475 That is crazy! I am not going to use ruby to do math. That is crazy! I am not going to use ruby to do math.

]]>