mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Jₑₙₛ Gustedt" <jens.gustedt@inria.fr>
To: JeanHeyd Meneide <phdofthehouse@gmail.com>
Cc: musl@lists.openwall.com, enh <enh@google.com>,
	"Rich Felker" <dalias@libc.org>,
	"罗勇刚(Yonggang Luo)" <luoyonggang@gmail.com>,
	"Jason Ekstrand" <jason@jlekstrand.net>
Subject: Re: [musl] C23 implications for C libraries
Date: Fri, 5 May 2023 08:56:41 +0200	[thread overview]
Message-ID: <20230505085641.1ae2ca91@inria.fr> (raw)
In-Reply-To: <CANHA4Oh+K1q5rUO2kPvEEx9oLhj0fJ=Z9dhG-9so-mJRVe_4ew@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1647 bytes --]

Hello,

on Thu, 4 May 2023 20:37:58 -0400 you (JeanHeyd Meneide
<phdofthehouse@gmail.com>) wrote:

> > 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. …

Yes, in general I am always amazed to see how diversive and inventive
C implementations are. So changing things even as innocent sounding
like a format specifier or adding new function identifiers that could
be conflicting with applications is usually watched very
closely. There are really a lot of C implementations out there, and
in general they use the design space that is offered to them.

For format specifiers this is even more complicated. There are C
libraries that provide interfaces to add such specifiers from user
space. So here the risk for conflicts can not easily be assessed by
WG14 (we don't have the data). So it should be left to the C library
implementors to assess this risk.

Thanks
Jₑₙₛ

-- 
:: ICube :::::::::::::::::::::::::::::: deputy director ::
:: Université de Strasbourg :::::::::::::::::::::: ICPS ::
:: INRIA Nancy Grand Est :::::::::::::::::::::::: Camus ::
:: :::::::::::::::::::::::::::::::::::: ☎ +33 368854536 ::
:: https://icube-icps.unistra.fr/index.php/Jens_Gustedt ::

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2023-05-05  6:56 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
2023-05-05  6:56                 ` Jₑₙₛ Gustedt [this message]
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=20230505085641.1ae2ca91@inria.fr \
    --to=jens.gustedt@inria.fr \
    --cc=dalias@libc.org \
    --cc=enh@google.com \
    --cc=jason@jlekstrand.net \
    --cc=luoyonggang@gmail.com \
    --cc=musl@lists.openwall.com \
    --cc=phdofthehouse@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.
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).