From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: GLIBC Devel <libc-alpha@sourceware.org>
Subject: [patch] Document '%F' format specifier
Date: Wed, 18 Jan 2023 18:43:58 -0800 [thread overview]
Message-ID: <CALoOobNE_v1z7WM5Js8-zpbuiFRr37Si0gCk13=wN2yBwDge_g@mail.gmail.com> (raw)
The '%F' specifier was implemented in commit 6c46718f9f0 on
2000-08-23, but remains undocumented in the manual.
https://stackoverflow.com/questions/75157669/format-specifier-f-missing-from-glibcs-documentation
Fix that.
--
Paul Pluzhnikov
diff --git a/manual/stdio.texi b/manual/stdio.texi
index f6319a4b8a..4f28646dd3 100644
--- a/manual/stdio.texi
+++ b/manual/stdio.texi
@@ -1845,8 +1845,9 @@ Print an integer as an unsigned hexadecimal
number. @samp{%x} uses
lower-case letters and @samp{%X} uses upper-case. @xref{Integer
Conversions}, for details.
-@item @samp{%f}
+@item @samp{%f}, @samp{%F}
Print a floating-point number in normal (fixed-point) notation.
+@samp{%f} uses lower-case letters and @samp{%F} uses upper-case.
@xref{Floating-Point Conversions}, for details.
@item @samp{%e}, @samp{%E}
@@ -2073,11 +2074,11 @@ various format options, using the template string:
@subsection Floating-Point Conversions
This section discusses the conversion specifications for floating-point
-numbers: the @samp{%f}, @samp{%e}, @samp{%E}, @samp{%g}, and @samp{%G}
-conversions.
+numbers: the @samp{%f}, @samp{%F}, @samp{%e}, @samp{%E}, @samp{%g}, and
+@samp{%G} conversions.
-The @samp{%f} conversion prints its argument in fixed-point notation,
-producing output of the form
+The @samp{%f} and @samp{%F} conversions print their argument in fixed-point
+notation, producing output of the form
@w{[@code{-}]@var{ddd}@code{.}@var{ddd}},
where the number of digits following the decimal point is controlled
by the precision you specify.
@@ -2123,7 +2124,7 @@ If the value to be printed represents infinity
or a NaN, the output is
@w{[@code{-}]@code{inf}} or @code{nan} respectively if the conversion
specifier is @samp{%a}, @samp{%e}, @samp{%f}, or @samp{%g} and it is
@w{[@code{-}]@code{INF}} or @code{NAN} respectively if the conversion is
-@samp{%A}, @samp{%E}, or @samp{%G}. On some implementations, a NaN
+@samp{%A}, @samp{%E}, @samp{%F} or @samp{%G}. On some implementations, a NaN
may result in longer output with information about the payload of the
NaN; ISO C2X defines a macro @code{_PRINTF_NAN_LEN_MAX} giving the
maximum length of such output.
next reply other threads:[~2023-01-19 2:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 2:43 Paul Pluzhnikov [this message]
2023-01-23 16:42 ` Siddhesh Poyarekar
2023-01-24 17:49 ` Paul Pluzhnikov
2023-01-24 21:32 ` Siddhesh Poyarekar
2023-01-24 22:20 ` Paul Pluzhnikov
2023-01-24 23:31 ` Siddhesh Poyarekar
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='CALoOobNE_v1z7WM5Js8-zpbuiFRr37Si0gCk13=wN2yBwDge_g@mail.gmail.com' \
--to=ppluzhnikov@google.com \
--cc=libc-alpha@sourceware.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).