From: Rich Felker <dalias@libc.org>
To: "Jₑₙₛ Gustedt" <jens.gustedt@inria.fr>
Cc: musl@lists.openwall.com
Subject: Re: [musl] printf("%lc", L'\0')
Date: Tue, 6 Jun 2023 10:19:19 -0400 [thread overview]
Message-ID: <20230606141919.GX4163@brightrain.aerifal.cx> (raw)
In-Reply-To: <20230606160708.3aab4a26@inria.fr>
On Tue, Jun 06, 2023 at 04:07:08PM +0200, Jₑₙₛ Gustedt wrote:
> Rich,
>
> on Tue, 6 Jun 2023 08:43:22 -0400 you (Rich Felker <dalias@libc.org>)
> wrote:
>
> > Is it really confirmed that all historical C implementations, not just
> > all historical POSIX ones, differ from the specification in this way?
>
> I personnally don't know much more than I posted in my question. AG
> tells us that musl is the only one they know about
>
> we are only aware of one (musl) that obeys a strict reading of
> the C standard.
>
> I don't know about historic implementations evidently.
The class AG is considering is likely POSIX/POSIXy implementations,
not all C implementations.
> > It would be nice to make sure they're informed and in agreement on
> > this, if there are any others.
>
> That will be one of the difficulties with a request that comes in so
> late in the procedure. We will have not much data to base our
> decision, but for the projects where the WG14 members are implicated
> in one way or another.
In that case I would probably lean towards asking AG to instead make a
change to (CX shaded) "it is unspecified whether a single zero byte is
written or the conversion has no output" and not imposing a change on
potentially unaware C implementations that have nothing to do with
POSIX, nor imposing a requirement to conflict with ISO C.
I really doubt there is anyone who cares about the specific behavior
in this case, but it seems unprofessional to do something like this
last-minute.
"Future directions" notes could be added that this might change.
Rich
next prev parent reply other threads:[~2023-06-06 14:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 10:02 Jₑₙₛ Gustedt
2023-06-06 12:43 ` Rich Felker
2023-06-06 14:07 ` Jₑₙₛ Gustedt
2023-06-06 14:19 ` Rich Felker [this message]
2023-06-06 14:29 ` Jₑₙₛ Gustedt
2023-06-24 13:21 ` Jₑₙₛ Gustedt
2023-06-24 17:24 ` Rich Felker
2023-06-25 7:26 ` Jₑₙₛ Gustedt
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=20230606141919.GX4163@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=jens.gustedt@inria.fr \
--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).