[GiNaC-list] Problem: Floating point overflow

[Richard B. Kreckel]

Hi!

Sheplyakov Alexei wrote:
> I used to think that GiNaC does not evaluate expressions numerically
> unless evalf() is called. Apparently this is not true. I think this
> is a bug which should be fixed.

Regarding .eval(), the idea is to evaluate numerically if and only if 
there is no exact value to be preserved. Integers and rationals are 
exact, floats not. Hence:
sin(3/2) -> sin(3/2)
sin(1.5) -> 0.9974949866040544309

Bye
   -richy.
-- 
Richard B. Kreckel
<http://www.ginac.de/~kreckel/>