public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bruno at clisp dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/30257] *printf of %lc with null argument should not produce a NUL byte
Date: Tue, 28 Mar 2023 17:45:50 +0000 [thread overview]
Message-ID: <bug-30257-131-uVdNQx7Thw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30257-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30257
--- Comment #2 from Bruno Haible <bruno at clisp dot org> ---
(In reply to Andreas Schwab from comment #1)
> Someone should submit a defect report to the C commitee.
Eric Blake has now opened a defect with POSIX, with the intent that both ISO C
and POSIX make the four *printf cases consistent:
https://austingroupbugs.net/view.php?id=1647
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-28 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 11:18 [Bug stdio/30257] New: " bruno at clisp dot org
2023-03-21 15:26 ` [Bug stdio/30257] " sam at gentoo dot org
2023-03-21 15:27 ` eblake at redhat dot com
2023-03-28 11:46 ` schwab@linux-m68k.org
2023-03-28 17:45 ` bruno at clisp dot org [this message]
2023-11-14 13:24 ` bruno at clisp dot org
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=bug-30257-131-uVdNQx7Thw@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).