From: Paul Eggert <eggert@cs.ucla.edu>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: Po Lu <luangruo@yahoo.com>, Richard Stallman <rms@gnu.org>,
eliz@gnu.org, contovob@tcd.ie, emacs-devel@gnu.org
Subject: Re: Lisp reader syntax and bootstrap
Date: Thu, 13 Jul 2023 23:57:24 -0700 [thread overview]
Message-ID: <d679a7a4-4bff-a1c0-69e4-fabd9e79f668@cs.ucla.edu> (raw)
In-Reply-To: <u4jm7nkvl@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 486 bytes --]
On 2023-07-13 22:05, Ulrich Mueller wrote:
> Maybe some wording like "approximates positive and negative infinities
> with the largest and smallest representable finite numbers" would be
> more accurate?
Unfortunately "smallest" connotes being close to zero. Also, I just
looked at the C Standard again, and it doesn't guarantee that HUGE_VAL
is the maximum 'double' on a VAX (!).
Anyway, thanks for pointing out the confusion. I installed the attached
to try to clear matters up.
[-- Attachment #2: 0001-Improve-doc-for-VAX-reading-NaN-INF.patch --]
[-- Type: text/x-patch, Size: 1250 bytes --]
From be501f468ed36cddf01305b88bab44366b447c03 Mon Sep 17 00:00:00 2001
From: Paul Eggert <eggert@cs.ucla.edu>
Date: Thu, 13 Jul 2023 23:36:33 -0700
Subject: [PATCH 1/2] Improve doc for VAX reading NaN, INF
* doc/lispref/numbers.texi (Float Basics): Improve description of
how Lisp reads infinities and NaNs on a VAX.
---
doc/lispref/numbers.texi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/lispref/numbers.texi b/doc/lispref/numbers.texi
index bcf89fc9ab1..a49afb73539 100644
--- a/doc/lispref/numbers.texi
+++ b/doc/lispref/numbers.texi
@@ -280,9 +280,9 @@ Float Basics
@code{(= 0.0 -0.0)} returns @code{t}.
Infinities and NaNs are not available on legacy systems that lack
-IEEE floating-point arithmetic. On a circa 1980 VAX, for example, the
-Lisp reader approximates an infinity with the nearest finite value,
-and a NaN with some other non-numeric Lisp object that provokes an
+IEEE floating-point arithmetic. On a circa 1980 VAX, for example,
+Lisp reads @samp{1.0e+INF} as a large but finite floating-point number,
+and @samp{0.0e+NaN} as some other non-numeric Lisp object that provokes an
error if used numerically.
Here are read syntaxes for these special floating-point values:
--
2.39.2
[-- Attachment #3: 0002-Reorder-NaN-INF-paras.patch --]
[-- Type: text/x-patch, Size: 1582 bytes --]
From 01b80a6f0e40a4390717a79a73c61899e2ec2968 Mon Sep 17 00:00:00 2001
From: Paul Eggert <eggert@cs.ucla.edu>
Date: Thu, 13 Jul 2023 23:55:50 -0700
Subject: [PATCH 2/2] Reorder NaN, INF paras
* doc/lispref/numbers.texi (Float Basics):
Reorder paragraphs so that examples follow defns.
---
doc/lispref/numbers.texi | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/doc/lispref/numbers.texi b/doc/lispref/numbers.texi
index a49afb73539..071ec0f518d 100644
--- a/doc/lispref/numbers.texi
+++ b/doc/lispref/numbers.texi
@@ -279,12 +279,6 @@ Float Basics
conversely, @code{(equal 0.0 -0.0)} returns @code{nil} whereas
@code{(= 0.0 -0.0)} returns @code{t}.
- Infinities and NaNs are not available on legacy systems that lack
-IEEE floating-point arithmetic. On a circa 1980 VAX, for example,
-Lisp reads @samp{1.0e+INF} as a large but finite floating-point number,
-and @samp{0.0e+NaN} as some other non-numeric Lisp object that provokes an
-error if used numerically.
-
Here are read syntaxes for these special floating-point values:
@table @asis
@@ -294,6 +288,12 @@ Float Basics
@samp{0.0e+NaN} and @samp{-0.0e+NaN}
@end table
+ Infinities and NaNs are not available on legacy systems that lack
+IEEE floating-point arithmetic. On a circa 1980 VAX, for example,
+Lisp reads @samp{1.0e+INF} as a large but finite floating-point number,
+and @samp{0.0e+NaN} as some other non-numeric Lisp object that provokes an
+error if used numerically.
+
The following functions are specialized for handling floating-point
numbers:
--
2.39.2
next prev parent reply other threads:[~2023-07-14 6:57 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 11:46 Disambiguate modeline character for UTF-8? Ulrich Mueller
2020-08-23 15:27 ` Stefan Monnier
2020-08-23 16:07 ` Eli Zaretskii
2020-08-23 18:24 ` Paul Eggert
2020-08-23 18:53 ` Ulrich Mueller
2020-08-23 18:56 ` Eli Zaretskii
2020-08-23 18:57 ` Eli Zaretskii
2020-08-23 19:13 ` Ulrich Mueller
2020-08-23 19:42 ` Eli Zaretskii
2020-08-23 21:23 ` Stefan Monnier
2020-08-24 7:06 ` Ulrich Mueller
2020-08-24 14:30 ` Yuri Khan
2020-08-29 11:17 ` Ulrich Mueller
2020-08-24 14:36 ` Drew Adams
2020-08-24 15:23 ` Ulrich Mueller
2020-08-24 16:43 ` Stefan Monnier
2023-07-05 10:08 ` Ulrich Mueller
2023-07-05 11:41 ` Eli Zaretskii
2023-07-05 13:04 ` Ulrich Mueller
2023-07-05 13:44 ` Eli Zaretskii
2023-07-05 21:50 ` Ulrich Mueller
2023-07-05 22:11 ` Paul Eggert
2023-07-06 8:51 ` Ulrich Mueller
2023-07-06 5:33 ` Eli Zaretskii
2023-07-06 8:47 ` Ulrich Mueller
2023-07-06 9:20 ` Eli Zaretskii
2023-07-06 9:46 ` Ulrich Mueller
2023-07-06 12:34 ` Po Lu
2023-07-06 12:32 ` Po Lu
2023-07-06 12:31 ` Po Lu
2023-07-06 13:02 ` Andreas Schwab
2023-07-06 13:08 ` Ulrich Mueller
2023-07-06 17:37 ` Paul Eggert
2023-07-06 18:13 ` Eli Zaretskii
2023-07-06 18:44 ` Ulrich Müller
2023-07-06 19:01 ` Eli Zaretskii
2023-07-06 19:31 ` Ulrich Mueller
2023-07-07 5:18 ` Eli Zaretskii
2023-07-07 5:48 ` Ulrich Müller
2023-07-07 6:16 ` Po Lu
2023-07-07 6:41 ` Ulrich Mueller
2023-07-07 7:38 ` Po Lu
2023-07-07 9:44 ` Ulrich Mueller
2023-07-07 10:21 ` Eli Zaretskii
2023-07-07 10:42 ` Ulrich Mueller
2023-07-07 12:04 ` Po Lu
2023-07-07 13:01 ` Ulrich Mueller
2023-07-07 13:38 ` Po Lu
2023-07-07 12:01 ` Po Lu
2023-07-07 12:38 ` Andreas Schwab
2023-07-07 13:37 ` Po Lu
2023-07-07 13:45 ` Andreas Schwab
2023-07-07 12:58 ` Eli Zaretskii
2023-07-08 8:49 ` Eli Zaretskii
2023-07-08 15:27 ` Basil Contovounesios
2023-07-08 15:38 ` Eli Zaretskii
2023-07-08 16:21 ` Basil Contovounesios
2023-07-08 16:33 ` Eli Zaretskii
2023-07-08 16:57 ` Basil Contovounesios
2023-07-08 18:21 ` Ulrich Mueller
2023-07-08 21:31 ` Basil Contovounesios
2023-07-09 9:22 ` Lisp reader syntax and bootstrap (was: Re: Disambiguate modeline character for UTF-8?) Ulrich Mueller
2023-07-09 9:57 ` Lisp reader syntax and bootstrap Po Lu
2023-07-13 2:04 ` Richard Stallman
2023-07-13 4:27 ` Po Lu
2023-07-13 22:07 ` Paul Eggert
2023-07-14 5:05 ` Ulrich Mueller
2023-07-14 6:57 ` Paul Eggert [this message]
2023-07-15 2:10 ` Richard Stallman
2023-07-15 2:38 ` Po Lu
2023-07-15 5:18 ` Philip Kaludercic
2023-07-15 5:50 ` Po Lu
2023-07-15 15:22 ` Paul Eggert
2023-07-17 2:22 ` Richard Stallman
2023-07-17 5:26 ` Paul Eggert
2023-07-17 2:32 ` Po Lu
2023-07-16 2:19 ` Richard Stallman
2023-07-09 11:35 ` Lisp reader syntax and bootstrap (was: Re: Disambiguate modeline character for UTF-8?) Eli Zaretskii
2023-07-07 0:19 ` Disambiguate modeline character for UTF-8? Po Lu
2023-07-06 12:27 ` Po Lu
2023-07-07 7:09 ` UTF-32 (was: Re: Disambiguate modeline character for UTF-8?) Ulrich Mueller
2023-07-07 7:34 ` Eli Zaretskii
2023-07-07 8:20 ` UTF-32 Ulrich Mueller
2023-07-07 10:16 ` UTF-32 Eli Zaretskii
2023-07-07 10:34 ` UTF-32 Ulrich Mueller
2023-07-07 12:49 ` UTF-32 Eli Zaretskii
2023-07-07 13:24 ` UTF-32 Andreas Schwab
2023-07-07 13:36 ` UTF-32 Ulrich Mueller
2023-07-07 14:06 ` UTF-32 Eli Zaretskii
2023-07-05 12:49 ` Disambiguate modeline character for UTF-8? Stefan Monnier
2023-07-05 13:38 ` Eli Zaretskii
2023-07-06 19:07 ` Filipp Gunbin
2020-08-23 19:47 ` Stefan Kangas
2020-08-24 18:35 ` Juri Linkov
2020-08-24 18:55 ` Eli Zaretskii
2020-08-25 18:59 ` Juri Linkov
2020-08-25 19:26 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d679a7a4-4bff-a1c0-69e4-fabd9e79f668@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=contovob@tcd.ie \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=rms@gnu.org \
--cc=ulm@gentoo.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.