[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 2/2] doc: explicitly mention 'inf' values in seq(1) documenta
From: |
Eric Blake |
Subject: |
Re: [PATCH 2/2] doc: explicitly mention 'inf' values in seq(1) documentation |
Date: |
Tue, 29 Jul 2014 13:33:33 -0600 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
On 07/29/2014 12:56 PM, Bernhard Voelker wrote:
> Thanks for the details.
> Would you mind providing a documentation patch?
How's this? If you like it, I'll turn it into a formal commit with
changelog.
diff --git i/doc/coreutils.texi w/doc/coreutils.texi
index 19a523d..96f0781 100644
--- i/doc/coreutils.texi
+++ w/doc/coreutils.texi
@@ -1069,11 +1069,14 @@ Floating point
input use the standard C functions @code{strtod} and @code{strtold} to
convert from text to floating point numbers. These floating point
numbers therefore can use scientific notation like @code{1.0e-34} and
-@code{-10e100}. Modern C implementations also accept hexadecimal
-floating point numbers such as @code{-0x.ep-3}, which stands for
-@minus{}14/16 times @math{2^-3}, which equals @minus{}0.109375. The
-@env{LC_NUMERIC} locale determines the decimal-point character.
-@xref{Parsing of Floats,,, libc, The GNU C Library Reference Manual}.
+@code{-10e100}. Commands that parse floating point also understand
+case-insensitive @code{inf}, @code{infinity}, and @code{NaN}, although
+whether such values are useful depends on the command in question.
+Modern C implementations also accept hexadecimal floating point
+numbers such as @code{-0x.ep-3}, which stands for @minus{}14/16 times
+@math{2^-3}, which equals @minus{}0.109375. The @env{LC_NUMERIC}
+locale determines the decimal-point character. @xref{Parsing of
+Floats,,, libc, The GNU C Library Reference Manual}.
@node Signal specifications
@section Signal specifications
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
- seq and infinite values, Bernhard Voelker, 2014/07/26
- [PATCH 1/2] seq: don't allow --equal-width option with infinite FIRST and LAST, Bernhard Voelker, 2014/07/26
- [PATCH 2/2] doc: explicitly mention 'inf' values in seq(1) documentation, Bernhard Voelker, 2014/07/26
- Re: [PATCH 2/2] doc: explicitly mention 'inf' values in seq(1) documentation, Pádraig Brady, 2014/07/26
- Re: [PATCH 2/2] doc: explicitly mention 'inf' values in seq(1) documentation, Bernhard Voelker, 2014/07/29
- Re: [PATCH 2/2] doc: explicitly mention 'inf' values in seq(1) documentation, Pádraig Brady, 2014/07/29
- Re: [PATCH 2/2] doc: explicitly mention 'inf' values in seq(1) documentation, Eric Blake, 2014/07/29
- Re: [PATCH 2/2] doc: explicitly mention 'inf' values in seq(1) documentation, Bernhard Voelker, 2014/07/29
- Re: [PATCH 2/2] doc: explicitly mention 'inf' values in seq(1) documentation,
Eric Blake <=
- Re: [PATCH 2/2] doc: explicitly mention 'inf' values in seq(1) documentation, Bernhard Voelker, 2014/07/29
- Re: [PATCH 2/2] doc: explicitly mention 'inf' values in seq(1) documentation, Eric Blake, 2014/07/29
- Re: [PATCH 2/2] doc: explicitly mention 'inf' values in seq(1) documentation, Eric Blake, 2014/07/29
- Re: [PATCH 2/2] doc: explicitly mention 'inf' values in seq(1) documentation, Bernhard Voelker, 2014/07/29
- Re: [PATCH 2/2] doc: explicitly mention 'inf' values in seq(1) documentation, Eric Blake, 2014/07/29