From: Rob Browning <rlb@defaultvalue.org>
Cc: Marius Vollmer <mvo@zagadka.ping.de>, guile-devel <guile-devel@gnu.org>
Subject: Re: IEEE Inf and NaN support for numbers.c
Date: Thu, 21 Mar 2002 18:59:04 -0600 [thread overview]
Message-ID: <87vgbp2zaf.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <15514.19909.408835.204209@segfault.bogus.domain> ("John W. Eaton"'s message of "Thu, 21 Mar 2002 15:16:53 -0600")
"John W. Eaton" <jwe@bevo.che.wisc.edu> writes:
> BTW, would people object to reformatting numbers.c to follow the GNU
> coding standards?
It wouldn't bother me, but I can't speak for everyone of course.
On a related note, I've been playing around here with replacing our
bignum support with gmp (and noticing some bugs that need fixing along
the way). The integration seems fairly easy (I've converted a lot of
the code in an very experimental tree), but I was wondering if you had
any thoughts on that front.
Thanks
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-22 0: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 ` 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 [this message]
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=87vgbp2zaf.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
--cc=mvo@zagadka.ping.de \
/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).