Wrapping up SRFI-70 Aubrey Jaffer (10 Aug 2005 03:16 UTC)
Re: Wrapping up SRFI-70 Bradley Lucier (10 Aug 2005 03:31 UTC)
Re: Wrapping up SRFI-70 Per Bothner (10 Aug 2005 05:13 UTC)
Re: Wrapping up SRFI-70 Aubrey Jaffer (15 Aug 2005 02:18 UTC)
Re: Wrapping up SRFI-70 Per Bothner (15 Aug 2005 16:38 UTC)
Re: Wrapping up SRFI-70 Aubrey Jaffer (18 Aug 2005 01:58 UTC)
Re: Wrapping up SRFI-70 Per Bothner (23 Aug 2005 00:24 UTC)
Re: Wrapping up SRFI-70 bear (10 Aug 2005 05:38 UTC)
Re: Wrapping up SRFI-70 Aubrey Jaffer (15 Aug 2005 03:45 UTC)
Re: Wrapping up SRFI-70 bear (17 Aug 2005 03:06 UTC)
Re: Wrapping up SRFI-70 Paul Schlie (17 Aug 2005 14:56 UTC)
Re: Wrapping up SRFI-70 bear (17 Aug 2005 17:00 UTC)
Re: Wrapping up SRFI-70 Aubrey Jaffer (19 Aug 2005 01:26 UTC)
Re: Wrapping up SRFI-70 bear (19 Aug 2005 18:28 UTC)

Re: Wrapping up SRFI-70 Aubrey Jaffer 15 Aug 2005 02:18 UTC

 | Date: Tue, 09 Aug 2005 22:13:23 -0700
 | From: Per Bothner <xxxxxx@bothner.com>
 |
 | I think there are some good things here, but there may be too much
 | stuff in one SRFI.
 |
 | ....
 |
 | An SRFI dealing with inexact infinities should I think focus more
 | on IEEE infinities.  It is desirable that a Scheme implementation
 | can map (possibly compile) Scheme arithmetic on inexact reals into
 | IEEE floating-point arithmetic.  I think more dicussion of this
 | issue is needed.

The current (2005/08/12) revision of SRFI-70 makes clear that +inf.0
and -inf.0 correspond to the IEEE-754 infinities already supported by
nine implementations of Scheme.

 | Date: Tue, 09 Aug 2005 22:36:32 -0700
 | From: Per Bothner <xxxxxx@bothner.com>
 |
 | The rationale discusses NaN, but I think the solution that
 | 0/0. = 0/0. is wrong.  I think it is important to be compatible
 | with IEEE, and that 0/0. be the same as NaN.

0/0 is now an optional error object, completely unconstrained by
SRFI-70.

 | The Kawa solution (which I think is the right one):
 |
 | (define NaN ...)
 | (= NaN NaN) => #f
 | (eq? NaN NaN) => #t
 | (eqv? NaN NaN) => #t
 | (equal? NaN NaN) => #t
 |
 | This may technically violate R5RS, but I think it's the
 | best choice if we want to be compatible with IEEE, which
 | think we do.

I believe that the junking of 0/0 makes SRFI-70 compatible with
IEEE-754.  Do you agree?