From: Vincent Lefevre <vincent@vinc17.net>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] printf.3: Document 'l' length modifier for a, A, e, E, f, F, g, and G
Date: Fri, 20 May 2022 18:11:21 +0200 [thread overview]
Message-ID: <20220520161121.GA1112518@zira.vinc17.org> (raw)
In-Reply-To: <ca8d1d17-4bde-6728-fa15-8655f3e14c3c@gmail.com>
On 2022-05-20 16:44:42 +0200, Alejandro Colomar wrote:
> Hi Vincent,
>
> On 5/20/22 16:10, Vincent Lefevre wrote:
> > Signed-off-by: Vincent Lefevre <vincent@vinc17.net>
> > ---
> > man3/printf.3 | 12 +++++++++++-
> > 1 file changed, 11 insertions(+), 1 deletion(-)
> >
> > diff --git a/man3/printf.3 b/man3/printf.3
> > index 4fa1f11f3..63ea3092f 100644
> > --- a/man3/printf.3
> > +++ b/man3/printf.3
> > @@ -502,7 +502,17 @@ argument, or a following
> > .B s
> > conversion corresponds to a pointer to
> > .I wchar_t
> > -argument.
> > +argument. In C99, on a following
>
> Why "in C99"?
According to GCC with "-Wformat -pedantic", this is new in C99:
warning: ISO C90 does not support the ‘%le’ gnu_printf format
The printf(3) man page already mentions features that appeared in
C99. For instance: "a, A (C99; not in SUSv2, but added in SUSv3)"
That's why I mentioned that for consistency.
I could also check that this is not in SUSv2:
https://pubs.opengroup.org/onlinepubs/7990989775/xsh/fprintf.html
Perhaps this should be rephrased. Something like:
On a following a, A, e, E, f, F, g, or G conversion, this
length modifier is ignored (C99; not in SUSv2).
What do you think?
I don't know about SUSv3 (I could just see that this feature was
also supported in POSIX:2004).
> Also, see man-pages(7):
>
> Use semantic newlines
> In the source of a manual page, new sentences should be
> started on new lines, long sentences should be split into
> lines at clause breaks (commas, semicolons, colons, and
> so on), and long clauses should be split at phrase bound‐
> aries. This convention, sometimes known as "semantic
> newlines", makes it easier to see the effect of patches,
> which often operate at the level of individual sentences,
> clauses, or phrases.
Thanks for the information.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
next prev parent reply other threads:[~2022-05-20 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 14:10 [PATCH] printf.3: Document 'l' length modifier for a, A, e, E, f, F, g, and G Vincent Lefevre
2022-05-20 14:44 ` Alejandro Colomar
2022-05-20 16:11 ` Vincent Lefevre [this message]
2022-05-20 16:18 ` Alejandro Colomar
2022-05-20 17:30 ` Vincent Lefevre
2022-05-21 17:17 ` Alejandro Colomar
2022-05-24 7:07 ` Stefan Puiu
2022-05-24 7:39 ` Vincent Lefevre
2022-05-24 12:23 ` Stefan Puiu
2022-05-24 13:57 ` Vincent Lefevre
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=20220520161121.GA1112518@zira.vinc17.org \
--to=vincent@vinc17.net \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.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