Nitpick with FLOOR etc. Michael Sperber (07 Jul 2005 08:46 UTC)
Re: Nitpick with FLOOR etc. Aubrey Jaffer (09 Jul 2005 00:50 UTC)
Re: Nitpick with FLOOR etc. Michael Sperber (11 Jul 2005 06:55 UTC)
Re: Nitpick with FLOOR etc. Aubrey Jaffer (16 Jul 2005 02:01 UTC)
Re: Nitpick with FLOOR etc. Paul Schlie (16 Jul 2005 08:38 UTC)
Re: Nitpick with FLOOR etc. Aubrey Jaffer (16 Jul 2005 17:42 UTC)
Re: Nitpick with FLOOR etc. Paul Schlie (16 Jul 2005 09:12 UTC)
Re: Nitpick with FLOOR etc. Aubrey Jaffer (16 Jul 2005 18:19 UTC)
Re: Nitpick with FLOOR etc. Paul Schlie (17 Jul 2005 17:23 UTC)
Re: Nitpick with FLOOR etc. Paul Schlie (17 Jul 2005 17:35 UTC)
Re: Nitpick with FLOOR etc. Aubrey Jaffer (17 Jul 2005 22:43 UTC)
Re: Nitpick with FLOOR etc. Paul Schlie (18 Jul 2005 01:43 UTC)
Re: Nitpick with FLOOR etc. Paul Schlie (18 Jul 2005 02:31 UTC)
Re: Nitpick with FLOOR etc. bear (18 Jul 2005 05:59 UTC)
Re: Nitpick with FLOOR etc. Aubrey Jaffer (18 Jul 2005 18:57 UTC)
Re: Nitpick with FLOOR etc. bear (19 Jul 2005 01:35 UTC)
Re: Nitpick with FLOOR etc. Alan Watson (19 Jul 2005 20:30 UTC)
Re: Nitpick with FLOOR etc. Aubrey Jaffer (21 Jul 2005 17:35 UTC)
Re: Nitpick with FLOOR etc. Aubrey Jaffer (24 Jul 2005 23:15 UTC)
Re: Nitpick with FLOOR etc. Paul Schlie (18 Jul 2005 03:24 UTC)
Re: Nitpick with FLOOR etc. Aubrey Jaffer (18 Jul 2005 18:24 UTC)
Re: Nitpick with FLOOR etc. Paul Schlie (18 Jul 2005 18:41 UTC)
Re: Nitpick with FLOOR etc. Aubrey Jaffer (21 Jul 2005 23:36 UTC)
Re: Nitpick with FLOOR etc. Paul Schlie (22 Jul 2005 00:50 UTC)
Re: Nitpick with FLOOR etc. Aubrey Jaffer (25 Jul 2005 00:54 UTC)
Re: Nitpick with FLOOR etc. bear (27 Jul 2005 15:56 UTC)
Re: Nitpick with FLOOR etc. Aubrey Jaffer (01 Aug 2005 16:33 UTC)
Re: Nitpick with FLOOR etc. Aubrey Jaffer (25 Jul 2005 01:16 UTC)
Re: Nitpick with FLOOR etc. Paul Schlie (25 Jul 2005 02:38 UTC)
Re: Nitpick with FLOOR etc. Aubrey Jaffer (28 Jul 2005 01:11 UTC)
Re: Nitpick with FLOOR etc. Paul Schlie (28 Jul 2005 18:15 UTC)
Re: Nitpick with FLOOR etc. Aubrey Jaffer (01 Aug 2005 16:59 UTC)
Re: Nitpick with FLOOR etc. Paul Schlie (02 Aug 2005 13:58 UTC)
Re: Nitpick with FLOOR etc. Aubrey Jaffer (18 Jul 2005 17:39 UTC)
Re: Nitpick with FLOOR etc. Paul Schlie (18 Jul 2005 18:15 UTC)
Re: Nitpick with FLOOR etc. Aubrey Jaffer (20 Jul 2005 19:24 UTC)
Re: Nitpick with FLOOR etc. Paul Schlie (20 Jul 2005 21:35 UTC)
Re: Nitpick with FLOOR etc. bear (20 Jul 2005 22:41 UTC)
Re: Nitpick with FLOOR etc. Paul Schlie (20 Jul 2005 22:47 UTC)
Re: Nitpick with FLOOR etc. Aubrey Jaffer (21 Jul 2005 01:31 UTC)

Re: Nitpick with FLOOR etc. Aubrey Jaffer 20 Jul 2005 19:25 UTC

 | Date: Mon, 18 Jul 2005 14:12:41 -0400
 | From: Paul Schlie <xxxxxx@comcast.net>
 |
 | > From: Aubrey Jaffer <xxxxxx@alum.mit.edu>
 | >    ...
 | > One might argue that large exact numbers being within the
 | > +/0. interval make them `=' to it.  But that foils transitivity for
 | > `=':
 | >
 | >   (= (expt 10 1000) +/0. (expt 10 999)
 | >
 | > Large exact numbers can not be greater than +/0. because the entire
 | > real line is covered by inexact neighborhoods in SRFI-70.
 | >
 | > So large exact numbers must be less than +/0..
 |
 | - maybe I misunderstand, but my attempted point was that since many
 | exact implementations enable the representation of value of greater
 | magnitude than the value range that an inexact infinity begins, it
 | seems incorrect to define that (> #i1/0 1e1000) if #i1/0 represents
 | all values greater than an inexact 1e306 for example.

For the purpose of comparisons, the nominal value (not the real
interval) of an inexact is used.  This is so that mixed comparisons
maintain total order with transitivity:

(let ((big-inex (expt 2. 100)))
  (< (- (inexact->exact big-inex) 1)
     big-inex
     (+ (inexact->exact big-inex) 1)))
			==> #t

For real infinities, there is no nominal value.  SRFI-70 chooses to
have them behave as though their values are upper and lower bounds of
all the finite real (exact and inexact) values an implementation
supports.

 | I would presume:
 |
 |  (> #i1/0 1e1000) => #f

Okay.  (number->string 1e1000) ==> #i+/0
If you meant #e1e1000, then the answer should be #t.

 | and
 |  (= #i1/0 1e1000) => #f

This should be #t for the same reason.
If you meant #e1e1000, then the answer should be #f; no finite
number should be equal to infinity.

 | yet
 |  (> #e1/0 1e1000) => #t
 |
 | assuming #e1/0 were unique from #i1/0, and representing all values
 | greater than the representational range of an exact implementation,
 | assuming that all implementations of exact have some practical
 | limit.  Thereby also:
 |
 |  (>= #e1/0 #i1/0) => #t ; as #i1/0 is a subset of #e1/0, not > or =.

Then we lose the total ordering of the reals.
Subset-of as a metric does not produce a total ordering.

Note that SRFI-70 does not specify where the border is between finite
and infinite numbers.  The spacing between the largest finite numbers
is very large:

(- 179.76931348623157e306 179.76931348623156e306)
				==> 1.99584030953472e+292

For adjoining neighborhoods, the border between them is the point
equidistant from their nominal values.  #i+/0 has no nominal value; so
we need not link its boundary to some nominal value we assign.
Picking a nominal value which is the same as an exact infinity nominal
value makes conversions between them work and preserves the total
order for mixed comparisons.