From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, Alyssa Ross <hi@alyssa.is>,
linux-man@vger.kernel.org
Subject: Re: [PATCH 1/5] scanf.3: clarify that %n supports type modifiers
Date: Mon, 5 Apr 2021 21:48:15 +0200 [thread overview]
Message-ID: <0d38058f-5b74-e22c-5df5-f5bb7643ba9b@gmail.com> (raw)
In-Reply-To: <20210405131307.2892-2-alx.manpages@gmail.com>
Hello Alex and Alyssa,
On 4/5/21 3:13 PM, Alejandro Colomar wrote:
> From: Alyssa Ross <hi@alyssa.is>
>
> My initial reading of this was that type modifiers were probably not
> supported. But they are, and this is actually documented further up,
> in the type modifiers documentation. But to make it clearer, let's
> copy the language that printf(3) has in its %n section.
>
> Signed-off-by: Alyssa Ross <hi@alyssa.is>
> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
> ---
> man3/scanf.3 | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/man3/scanf.3 b/man3/scanf.3
> index e6d00c9f1..bd49a6caf 100644
> --- a/man3/scanf.3
> +++ b/man3/scanf.3
> @@ -526,7 +526,9 @@ the next pointer must be a pointer to a pointer to
> Nothing is expected; instead, the number of characters consumed thus far
> from the input is stored through the next pointer, which must be a pointer
> to
> -.IR int .
> +.IR int ,
> +or variant whose size matches the (optionally)
> +supplied integer length modifier.
> This is
> .I not
> a conversion and does
Thanks. Patch applied.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2021-04-05 19:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 13:13 [PATCH 0/5] Merged patches from others Alejandro Colomar
2021-04-05 13:13 ` [PATCH 1/5] scanf.3: clarify that %n supports type modifiers Alejandro Colomar
2021-04-05 19:48 ` Michael Kerrisk (man-pages) [this message]
2021-04-05 13:13 ` [PATCH 2/5] userfaultfd.2: Add UFFD_FEATURE_THREAD_ID docs Alejandro Colomar
2021-04-05 19:56 ` Michael Kerrisk (man-pages)
2021-04-05 20:01 ` Michael Kerrisk (man-pages)
2021-04-05 13:13 ` [PATCH 3/5] userfaultfd.2: Add write-protect mode Alejandro Colomar
2021-04-05 21:13 ` Michael Kerrisk (man-pages)
2021-04-06 16:36 ` Peter Xu
2021-04-05 13:13 ` [PATCH 4/5] ioctl_userfaultfd.2: Add UFFD_FEATURE_THREAD_ID docs Alejandro Colomar
2021-04-05 21:13 ` Michael Kerrisk (man-pages)
2021-04-05 13:13 ` [PATCH 5/5] ioctl_userfaultfd.2: Add write-protect mode docs Alejandro Colomar
2021-04-05 21:14 ` Michael Kerrisk (man-pages)
2021-04-06 8:10 ` [PATCH 0/5] Merged patches from others Michael Kerrisk (man-pages)
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=0d38058f-5b74-e22c-5df5-f5bb7643ba9b@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=hi@alyssa.is \
--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