Thank you, i was porting my code from 1.6.7 to the new version where it
broke and I forgot about this. time for a m-x tags-search!
--rick
This happens because Guile now has exact rationals. This NEWS entry
explains the behavior:
** inexact->exact no longer returns only integers.
Without
Rick Taube <[EMAIL PROTECTED]> writes:
> this behavior of inexact->exact in guile 1.7.1 causes my program to
> become confused:
>
> guile> (inexact->exact 48.0)
> 48
> guile> (inexact->exact (* .1 480.0))
> 48
> guile> (inexact->exact (* (- 1.1 1) 480.0))
> 3377699720527875/70368744177664
This ha
Rick Taube wrote:
this behavior of inexact->exact in guile 1.7.1 causes my program to
become confused:
I suspect you're the one who is confused.
You need to learn about floating-point arithmetic.
(- 1.1 1) does not necessarily give the same result as 0.1.
i attempted to see if guile 1.7.2 fixes th
this behavior of inexact->exact in guile 1.7.1 causes my program to
become confused:
guile> (inexact->exact 48.0)
48
guile> (inexact->exact (* .1 480.0))
48
guile> (inexact->exact (* (- 1.1 1) 480.0))
3377699720527875/70368744177664
guile>(quit)
$ uname -a
Darwin pinhead.music.uiuc.edu 7.8.0 Darw
