mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Jₑₙₛ Gustedt" <jens.gustedt@inria.fr>
Cc: musl@lists.openwall.com
Subject: Re: [musl] printf("%lc", L'\0')
Date: Sat, 24 Jun 2023 15:21:55 +0200	[thread overview]
Message-ID: <20230624152155.2e011149@inria.fr> (raw)
In-Reply-To: <20230606124322.GW4163@brightrain.aerifal.cx>

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

Rich,

on Tue, 6 Jun 2023 08:43:22 -0400 you (Rich Felker <dalias@libc.org>)
wrote:

> On Tue, Jun 06, 2023 at 12:02:15PM +0200, Jₑₙₛ Gustedt wrote:
> > Hello,
> > the Austin Group has a bug at
> > 
> > 	https://austingroupbugs.net/view.php?id=1647
> > 
> > that lead to a (quite late) ballot comment for C23. It seems that
> > musl is the only implementation here that plays by the book and has
> > no byte of output at all for this call
> > 
> >      printf("%lc", L'\0');
> > 
> > All others seem to be more consistent with the other "c" output
> > formats and print one NUL byte.
> > 
> > Are there any feelings if we are going to change this in the sense
> > as AG proposes?  
> 
> Provided the change is to be aligned between POSIX and ISO C, and that
> all existing historical implementations except musl do the thing
> that's proposed, I don't think I have any objection to the change.
> It's a little more work and less elegant on the implementation side.

In this week's last round of ballot resolution WG14 chose option 1, so
this change.

> Is it really confirmed that all historical C implementations, not just
> all historical POSIX ones, differ from the specification in this way?
> That seems rather surprising (and amusing that nobody else bothered to
> read the spec when implementing). It would be nice to make sure
> they're informed and in agreement on this, if there are any others.

There was only time to check this for implementation that were there
(in particular IBM) but WG14 chose to do this regardless of this lack of
information.



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 --]

  parent reply	other threads:[~2023-06-24 13:22 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
2023-06-06 14:29       ` Jₑₙₛ Gustedt
2023-06-24 13:21   ` Jₑₙₛ Gustedt [this message]
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=20230624152155.2e011149@inria.fr \
    --to=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).