From: Rich Felker <dalias@libc.org>
To: Bruno Haible <bruno@clisp.org>
Cc: musl@lists.openwall.com
Subject: Re: [musl] *printf %lc of L'\0'
Date: Tue, 14 Nov 2023 10:38:04 -0500 [thread overview]
Message-ID: <20231114153804.GW4163@brightrain.aerifal.cx> (raw)
In-Reply-To: <4798297.Es0HkHt82z@nimes>
On Tue, Nov 14, 2023 at 02:22:46PM +0100, Bruno Haible wrote:
> Hi,
>
> On 2023-03-21 I noticed a bug with %lc in most libcs:
> <https://lists.gnu.org/archive/html/bug-gnulib/2023-03/msg00080.html>.
>
> On 2023-03-28 Eric Blake 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>
>
> This issue was then submitted in the ISO C 23 ballot as GB-141,
> and in the meeting from 2023-06-20 to 2023-06-23 it was decided upon:
> <https://www.open-std.org/JTC1/sc22/wg14/www/docs/n3167.pdf>
> page 23, 24. The decision ("option 1") is detailed in
> <https://www.open-std.org/JTC1/sc22/wg14/www/docs/n3148.doc>:
> "Option 1 (require a NUL) - change the text to:
> If an l length modifier is present, the wint_t argument is converted
> as if by a call to the wcrtomb function with a pointer to storage of
> at least MB_CUR_MAX bytes, the wint_t argument converted to wchar_t,
> and an initial shift state."
>
> So, ISO C changed, and POSIX will follow suit.
>
> The bug in most libcs is thus no longer a bug.
Yep, I have a patch for it as of a few days ago, which should make it
in the next release.
> musl libc, which had it correct, now has a bug.
Well, not a "bug" until the next standard is published and we claim
aiming to support it, but yes, something that should be changed. :-)
Rich
prev parent reply other threads:[~2023-11-14 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 13:22 Bruno Haible
2023-11-14 15:38 ` Rich Felker [this message]
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=20231114153804.GW4163@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=bruno@clisp.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).