From: Mark H Weaver <mhw@netris.org>
To: guile-devel@gnu.org
Subject: [PATCH] Fix and combine NEWS entries on `infinite?' and `finite?'
Date: Tue, 01 Feb 2011 04:47:06 -0500 [thread overview]
Message-ID: <87oc6ww0h1.fsf@yeeloong.netris.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 45 bytes --]
Another small and obvious patch.
Mark
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Fix and combine NEWS entries on `infinite?' and `finite?' --]
[-- Type: text/x-diff, Size: 1266 bytes --]
From 13e427d5c3e8eddbe48fcc31d6012cf31172e802 Mon Sep 17 00:00:00 2001
From: Mark H Weaver <mhw@netris.org>
Date: Tue, 1 Feb 2011 04:40:33 -0500
Subject: [PATCH] Fix and combine NEWS entries on `infinite?' and `finite?'
* NEWS: Fix and combine NEWS entries on `infinite?' and `finite?'.
Previous, they stated that these predicates now work on non-real
complex numbers, but that is not the case.
---
NEWS | 11 ++---------
1 files changed, 2 insertions(+), 9 deletions(-)
diff --git a/NEWS b/NEWS
index 3770cde..2ba79a6 100644
--- a/NEWS
+++ b/NEWS
@@ -186,15 +186,8 @@ remainder operators' for more information.
**** `infinite?' changes
-`infinite?' now returns #t for non-real complex infinities, and throws
-exceptions for non-numbers. (Note that NaNs _are_ considered numbers
-by scheme, despite their name).
-
-**** `finite?' changes
-
-`finite?' now returns #f for NaNs and non-real complex infinities, and
-throws exceptions for non-numbers. (Note that NaNs _are_ considered
-numbers by scheme, despite their name).
+`infinite?' and `finite?' now throw exceptions for non-numbers. (Note
+that NaNs _are_ considered numbers by scheme, despite their name).
**** `real-valued?', `rational-valued?' and `integer-valued?' changes
--
1.5.6.5
reply other threads:[~2011-02-01 9:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87oc6ww0h1.fsf@yeeloong.netris.org \
--to=mhw@netris.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).