From 01b80a6f0e40a4390717a79a73c61899e2ec2968 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Thu, 13 Jul 2023 23:55:50 -0700 Subject: [PATCH] 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 @@ whether they are numerically equal. For example, when @var{x} and 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 @@ Here are read syntaxes for these special floating-point values: @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.5