From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: IEEE Inf and NaN support for numbers.c
Date: 14 Mar 2002 21:59:17 +0100 [thread overview]
Message-ID: <87lmcuyifu.fsf@zagadka.ping.de> (raw)
In-Reply-To: <15494.39950.119995.223196@segfault.bogus.domain>
"John W. Eaton" <jwe@bevo.che.wisc.edu> writes:
> The following patch adds basic IEEE Inf and NaN support for guile. This
> introduces two new predicates (inf? and nan?) and two new functions
> (inf and nan, which return IEEE Infinity and NaN values,
> respectively).
Nice, thanks.
> guile> (/ 0)
> Inf
This is not a good print syntax for the new "inf" value. It looks
like a symbol, while it really is a number. Likewise for "NaN".
What about using "1/0" for inf and "0/0" for NaN. Does this fit with
the IEEE rules?
When this works, we don't need the 'inf' and 'nan' procedures.
Do we want to care about signalling versus quiet NaNs, and the extra
information in the mantissa of NaNs? (I don't think so.)
Also, somewhat unrelated to your patch, Guile can not read the
(illegal) notation "#.#" that is produces for funny numbers. It's
probably best to avoid outputting this notation altogether and just
find a way to cope with funny numbers more sanely. (Like you just did
for infinity.)
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next parent reply other threads:[~2002-03-14 20:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15494.39950.119995.223196@segfault.bogus.domain>
2002-03-14 20:59 ` Marius Vollmer [this message]
2002-03-21 21:16 ` IEEE Inf and NaN support for numbers.c John W. Eaton
2002-03-22 0:59 ` Rob Browning
2002-03-22 9:18 ` Neil Jerram
2002-04-24 19:11 ` Marius Vollmer
2002-04-24 21:07 ` John W. Eaton
2002-04-24 22:31 ` Marius Vollmer
2002-05-06 22:39 ` Marius Vollmer
2002-05-15 5:36 ` John W. Eaton
2002-05-15 19:27 ` Marius Vollmer
2002-04-24 22:51 ` Rob Browning
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=87lmcuyifu.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-devel@gnu.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).