From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Paul Pluzhnikov <ppluzhnikov@google.com>,
GLIBC Devel <libc-alpha@sourceware.org>
Subject: Re: [patch] Document '%F' format specifier
Date: Mon, 23 Jan 2023 11:42:19 -0500 [thread overview]
Message-ID: <129eebb5-6a60-5ab1-9e95-6c35b61111cc@gotplt.org> (raw)
In-Reply-To: <CALoOobNE_v1z7WM5Js8-zpbuiFRr37Si0gCk13=wN2yBwDge_g@mail.gmail.com>
On 2023-01-18 21:43, Paul Pluzhnikov via Libc-alpha wrote:
> 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.
>
The patch fails to apply on master. Also, the specifier needs to be
mentioned in the Floating-Point Conversions section alongside %f
wherever applicable. Other than the first line that mentions all format
specifiers, there are lines like:
The @samp{%g} and @samp{%G} conversions print the argument in the style
of @samp{%e} or @samp{%E} (respectively) if the exponent would be less
than -4 or greater than or equal to the precision; otherwise they use
the @samp{%f} style.
where I think mentioning @samp{%F} would be useful. i.e. wherever the
lower and upper options are mention together, do the same for %f too.
Please also review other sections in stdio.texi that mention %f and add
%F wherever applicable, e.g. input conversions.
Thanks,
Sid
next prev parent reply other threads:[~2023-01-23 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 2:43 Paul Pluzhnikov
2023-01-23 16:42 ` Siddhesh Poyarekar [this message]
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=129eebb5-6a60-5ab1-9e95-6c35b61111cc@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=libc-alpha@sourceware.org \
--cc=ppluzhnikov@google.com \
/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).