From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: [PATCH] Fix non-portable usage of `isinf' in `max' and `min'
Date: Thu, 03 Feb 2011 14:07:15 +0100 [thread overview]
Message-ID: <87bp2t9sho.fsf@gnu.org> (raw)
In-Reply-To: 87lj1yt0it.fsf_-_@yeeloong.netris.org
Hello!
And thanks for the patch stream and quick fixes! :-)
Mark H Weaver <mhw@netris.org> writes:
> Ah, I was using a non-portable extension of isinf(x) to determine the
> sign of the infinity. This patch should fix it.
We use Gnulib’s ‘isinf’ module. It could be that it’s buggy, or it
could be improved to handle this specific case, in which it would be
nice to share with bug-gnulib@gnu.org.
Ludo’.
next prev parent reply other threads:[~2011-02-03 13:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 11:25 [PATCH] Complex numbers with inexact zero imaginary part, etc Mark H Weaver
2011-02-02 20:29 ` Andy Wingo
2011-02-02 20:30 ` Andy Wingo
2011-02-02 21:36 ` Mark H Weaver
2011-02-02 22:42 ` Andy Wingo
2011-02-03 0:38 ` [PATCH] Fix non-portable usage of `isinf' in `max' and `min' Mark H Weaver
2011-02-03 9:43 ` Andy Wingo
2011-02-03 13:07 ` Ludovic Courtès [this message]
2011-02-02 20:35 ` [PATCH] Complex numbers with inexact zero imaginary part, etc Andy Wingo
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=87bp2t9sho.fsf@gnu.org \
--to=ludo@gnu.org \
--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).