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: 25 Apr 2002 00:31:12 +0200 [thread overview]
Message-ID: <87662gd8zz.fsf@zagadka.ping.de> (raw)
In-Reply-To: <15559.7841.142286.603654@segfault.bogus.domain>
"John W. Eaton" <jwe@bevo.che.wisc.edu> writes:
> On 24-Apr-2002, Marius Vollmer <mvo@zagadka.ping.de> wrote:
>
> | The cleanest way that I can think of right now is to use the
> | hash-comma reader extension:
> |
> | #,(+inf) #,(-inf) #,(nan) #,(nan 0.42345)
>
> I'm afraid I don't understand what
>
> #,(nan 0.42345)
>
> means.
That was meant to represent a NaN with additional information. As far
as I know, there are some unused bits in the mantissa of a IEEE NaN
that can be used to further characterize the NaN. I don't know of any
application of them, tho.
> It is easy enough to fix the patch so that it will write out these
> values any way you like. But I don't know enough about guile to know
> what to modify to make it read these forms.
Ok. I think we should follow PLT Scheme here. I will apply your
patch and make the necessary changes.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-04-24 22:31 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 ` IEEE Inf and NaN support for numbers.c Marius Vollmer
2002-03-21 21:16 ` 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 [this message]
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=87662gd8zz.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).