From: Robert Brown <rob99brown@...>
Date: 2007-07-17T14:50:18+09:00
Subject: Re: Force calculation result to BigDecimal


> Here's a quick fix.  There may be a better way to handle this, though.
>  Again, I'll give the usual warning about modifying core classes: you
> shouldn't normally do it unless you can be certain it won't break
> yours or anyone else's code.

Thanks Todd...

What are the risks in modifying core classes?  I've already done this a 
little by adding .round(n) to BigDecimal, where n is the decimal places.

Appreciate your tip, but I was thinking the other way round: have 
BigDecimal take Float as an initializer, not have Float output 
BigDecimal.

But this is all by-the-by.  What I'm really looking for is BigDecimal 
math, not Float, in my calculations (when there's a mixture of 
BigDecimal, Float and Fixnum types).

Still looking for suggestions on how I can do this better than manual 
type-checking and casting...


Thanks,

-- 
Posted via http://www.ruby-forum.com/.