From: bil@ccrma.Stanford.EDU
To: Mark H Weaver <mhw@netris.org>
Cc: 30426@debbugs.gnu.org
Subject: bug#30426: division inconsistency?
Date: Mon, 12 Feb 2018 13:59:24 -0800 [thread overview]
Message-ID: <8d11fe9992e70af48db00d9a35a93a20@ccrma.stanford.edu> (raw)
In-Reply-To: <87sha5q588.fsf@netris.org>
Thanks very much for the informative answer! I am not sure what
(* 0 +nan.0) should return. I lean toward +nan.0 mainly because
I assume NaNs exist to indicate an error somewhere, and you want
that to be returned. For (* 0 +inf.0) I have no druthers.
For (/ 0.0 0) and (/ +nan.0 0) s7 throws a divide-by-zero error,
but I have no good reason for doing this. In s7, I'd prefer
to say (/ x y ...) is equal to (/ x (* y ...)) in all cases.
next prev parent reply other threads:[~2018-02-12 21:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 22:56 bug#30426: division inconsistency? bil
2018-02-12 21:01 ` Mark H Weaver
2018-02-12 21:15 ` Mark H Weaver
2018-02-12 21:59 ` bil [this message]
2018-02-14 20:54 ` Mark H Weaver
2018-02-14 22:10 ` bil
2018-02-15 7:35 ` Mark H Weaver
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=8d11fe9992e70af48db00d9a35a93a20@ccrma.stanford.edu \
--to=bil@ccrma.stanford.edu \
--cc=30426@debbugs.gnu.org \
--cc=mhw@netris.org \
/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).