All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Vincent Lefevre <vincent@vinc17.net>
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:18:48 +0200	[thread overview]
Message-ID: <f5fef324-4883-197e-1e3d-e3b5b36ceaf9@gmail.com> (raw)
In-Reply-To: <20220520161121.GA1112518@zira.vinc17.org>

Hi Vincent,

On 5/20/22 18:11, Vincent Lefevre wrote:
>> 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

Ok.

> 
> 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?

Makes sense.  Since SUSv3 should be identical to POSIX.2001, which 
itself should be aligned with C99 (see standards(7)), we can just ignore 
it, or we can add it if you want.


> 
> I don't know about SUSv3 (I could just see that this feature was
> also supported in POSIX:2004).
> 

Please send a new patch.

Thanks,

Alex

-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

  reply	other threads:[~2022-05-20 16:19 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
2022-05-20 16:18     ` Alejandro Colomar [this message]
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=f5fef324-4883-197e-1e3d-e3b5b36ceaf9@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=vincent@vinc17.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.