From: Alejandro Colomar <alx.manpages@gmail.com>
To: bugzilla-daemon@kernel.org, linux-man@vger.kernel.org
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
Avinash Sonawane <rootkea@gmail.com>,
glibc <libc-alpha@sourceware.org>, GCC <gcc@gcc.gnu.org>
Subject: [PATCH] [Bug 215844] scanf.3: Clarify ll and L modifiers
Date: Sat, 16 Apr 2022 20:19:43 +0200 [thread overview]
Message-ID: <20220416181942.5464-1-alx.manpages@gmail.com> (raw)
Relevant documents:
POSIX:
<https://pubs.opengroup.org/onlinepubs/9699919799/functions/fscanf.html>
glibc:
<https://www.gnu.org/software/libc/manual/html_mono/libc.html#Numeric-Input-Conversions>
ISO C2x:
<http://www.open-std.org/JTC1/SC22/WG14/www/docs/n2731.pdf#subsubsection.7.21.6.2>
Still, from the documentation linked above, it seems to me that
"%Ln" is supported as a glibc extension, and doesn't fall into
"either no effect or undefined behavior" as says the GCC warning
shown in the bugzilla report. I didn't modify the documentation
regarding %n, and recommend investigating a possible GCC bug.
Reported-by: Avinash Sonawane <rootkea@gmail.com>
Link: bugzilla <https://bugzilla.kernel.org/show_bug.cgi?id=215844>
Cc: glibc <libc-alpha@sourceware.org>
Cc: GCC <gcc@gcc.gnu.org>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
---
man3/scanf.3 | 35 ++++++++++++++++++++++++++---------
1 file changed, 26 insertions(+), 9 deletions(-)
diff --git a/man3/scanf.3 b/man3/scanf.3
index 55058f3d2..199c8a19a 100644
--- a/man3/scanf.3
+++ b/man3/scanf.3
@@ -308,10 +308,6 @@ and the next pointer is a pointer to
.I double
(rather than
.IR float ).
-Specifying two
-.B l
-characters is equivalent to
-.BR L .
If used with
.B %c
or
@@ -320,12 +316,33 @@ the corresponding parameter is considered
as a pointer to a wide character or wide-character string respectively.
.\" This use of l was introduced in Amendment 1 to ISO C90.
.TP
+.B ll
+(ell-ell)
+Indicates that the conversion will be one of
+.BR b ,
+.BR d ,
+.BR i ,
+.BR o ,
+.BR u ,
+.BR x ,
+.BR X ,
+or
+.B n
+and the next pointer is a pointer to a
+.I long long
+or
+.I unsigned long long
+(rather than
+.IR int ).
+.TP
.B L
Indicates that the conversion will be either
\fBe\fP, \fBf\fP, or \fBg\fP
and the next pointer is a pointer to
.I "long double"
-or the conversion will be
+or
+(as a GNU extension)
+the conversion will be
\fBd\fP, \fBi\fP, \fBo\fP, \fBu\fP, or \fBx\fP
and the next pointer is a pointer to
.IR "long long" .
@@ -683,17 +700,17 @@ floating-point conversion specifier (and is unaffected by
etc.).
.SH BUGS
All functions are fully C89 conformant, but provide the
-additional specifiers
+additional modifiers
.B q
and
.B a
as well as an additional behavior of the
.B L
and
-.B l
-specifiers.
+.B ll
+modifiers.
The latter may be considered to be a bug, as it changes the
-behavior of specifiers defined in C89.
+behavior of modifiers defined in C89.
.PP
Some combinations of the type modifiers and conversion
specifiers defined by ANSI C do not make sense
--
2.30.2
reply other threads:[~2022-04-16 18:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220416181942.5464-1-alx.manpages@gmail.com \
--to=alx.manpages@gmail.com \
--cc=bugzilla-daemon@kernel.org \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=rootkea@gmail.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).