unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Cc: Aubrey Jaffer <agj@alum.mit.edu>
Subject: Re: bug in eqv?
Date: Sat, 25 Mar 2006 08:56:43 +1100	[thread overview]
Message-ID: <87zmjf4ick.fsf@zip.com.au> (raw)
In-Reply-To: <20060324001753.623721B77C9@home.voluntocracy.org> (Aubrey Jaffer's message of "Thu, 23 Mar 2006 19:17:53 -0500 (EST)")

Aubrey Jaffer <agj@alum.mit.edu> writes:
>
> SRFI-77 is the most preliminary of proposals, and guaranteed to be
> withdrawn.

Yep.  Seems to me the idea of base r5rs is reasonably clear (not
crystal clear, but near enough) that eqv? is the same as = on numbers.
Keeps the heirarchy of comparisons clean too.

>  -- library procedure: equal? obj1 obj2
>      `Equal?' recursively compares the contents of pairs, vectors, and
>      strings, applying `eqv?' on other objects such as numbers and
>      symbols.  A rule of thumb is that objects are generally `equal?'
>      if they print the same.  `Equal?' may fail to terminate if its
>      arguments are circular data structures.
>
> If -0.0 and 0.0 print differently, then there is no support for 
> (equal? -0.0 0.0) ==> #t.

I would read it that equal? is supposed to be the same as eqv? on
numbers, and the bit about printing is only an aid to understanding
the recursion (and not a terribly helpful one really).


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile


      reply	other threads:[~2006-03-24 21:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-18  3:42 bug in eqv? Aubrey Jaffer
2006-03-21  0:58 ` Kevin Ryde
2006-03-21 23:52   ` Marius Vollmer
2006-03-24  0:17     ` Aubrey Jaffer
2006-03-24 21:56       ` Kevin Ryde [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zmjf4ick.fsf@zip.com.au \
    --to=user42@zip.com.au \
    --cc=agj@alum.mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).