From: JeanHeyd Meneide <phdofthehouse@gmail.com>
To: musl@lists.openwall.com
Cc: enh <enh@google.com>, "Rich Felker" <dalias@libc.org>,
"Jₑₙₛ Gustedt" <jens.gustedt@inria.fr>,
"罗勇刚(Yonggang Luo)" <luoyonggang@gmail.com>,
"Jason Ekstrand" <jason@jlekstrand.net>
Subject: Re: [musl] C23 implications for C libraries
Date: Thu, 4 May 2023 20:37:58 -0400 [thread overview]
Message-ID: <CANHA4Oh+K1q5rUO2kPvEEx9oLhj0fJ=Z9dhG-9so-mJRVe_4ew@mail.gmail.com> (raw)
In-Reply-To: <9ecc996a-5eba-404d-1b95-63398ea93543@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
> for example, stuff like the %B specifier are technically optional given
that the uppercase conversion specifier namespace wasn't reserved, but iirc
there's no known implementation of C that uses it for any > other purpose.
There was apparently one implementation that was already using %B as a
kind of numeric printout (not for binary) that was reported during the
meeting and at a few other junctures, so unfortunately it might not be
fully portable. But, I think that for that implementation it's flag-guarded
(though on by default). It'd be great if I remembered the name of the
implementation (but the meeting this was discussed in was... over a year
ago now? So I'd have to go back and refresh my memory). If I do remember, I
thought to myself that I might send an e-mail asking them if they would
feel okay with aligning their library with the standard's recommendations.
Couldn't hurt to ask, right?
- JeanHeyd
[-- Attachment #2: Type: text/html, Size: 1092 bytes --]
next prev parent reply other threads:[~2023-05-05 0:38 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 14:25 Jₑₙₛ Gustedt
2022-09-23 14:58 ` Rich Felker
2022-09-23 15:11 ` Alexander Monakov
2022-09-23 15:35 ` Jₑₙₛ Gustedt
2022-09-23 15:28 ` enh
2022-09-23 15:40 ` Jₑₙₛ Gustedt
2022-09-23 23:52 ` enh
2022-09-24 7:31 ` Jₑₙₛ Gustedt
2022-09-26 3:18 ` Damian McGuckin
2022-09-26 3:33 ` Rich Felker
2022-09-26 10:49 ` Florian Weimer
2022-09-26 12:52 ` Jₑₙₛ Gustedt
2022-09-26 20:13 ` enh
2022-11-18 20:46 ` 罗勇刚(Yonggang Luo)
2022-11-19 14:33 ` Jₑₙₛ Gustedt
2022-11-19 17:19 ` 罗勇刚(Yonggang Luo)
2022-11-20 8:23 ` Jₑₙₛ Gustedt
2022-11-19 18:28 ` Rich Felker
2022-11-20 8:42 ` Jₑₙₛ Gustedt
2023-05-03 22:58 ` enh
2023-05-04 6:19 ` Jₑₙₛ Gustedt
2023-05-04 16:03 ` Rich Felker
2023-05-04 16:07 ` enh
2023-05-04 23:16 ` Gabriel Ravier
2023-05-05 0:37 ` JeanHeyd Meneide [this message]
2023-05-05 6:56 ` Jₑₙₛ Gustedt
2023-05-05 12:40 ` Rich Felker
2023-05-05 6:40 ` Jₑₙₛ Gustedt
2023-05-04 16:03 ` enh
2023-05-04 23:11 ` Gabriel Ravier
2022-11-19 18:31 ` Rich Felker
2022-11-20 4:25 ` 罗勇刚(Yonggang Luo)
2022-11-20 5:34 ` Markus Wichmann
2022-11-21 11:46 ` Reini Urban
2022-11-21 21:06 ` Jₑₙₛ Gustedt
2022-11-23 4:31 ` 罗勇刚(Yonggang Luo)
2022-11-23 8:11 ` Jₑₙₛ Gustedt
2022-11-23 8:20 ` 罗勇刚(Yonggang Luo)
2022-11-23 8:33 ` Jₑₙₛ Gustedt
2022-11-23 8:41 ` 罗勇刚(Yonggang Luo)
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='CANHA4Oh+K1q5rUO2kPvEEx9oLhj0fJ=Z9dhG-9so-mJRVe_4ew@mail.gmail.com' \
--to=phdofthehouse@gmail.com \
--cc=dalias@libc.org \
--cc=enh@google.com \
--cc=jason@jlekstrand.net \
--cc=jens.gustedt@inria.fr \
--cc=luoyonggang@gmail.com \
--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).