From: Rich Felker <dalias@libc.org>
To: "Jₑₙₛ Gustedt" <jens.gustedt@inria.fr>
Cc: enh <enh@google.com>, musl@lists.openwall.com
Subject: Re: [musl] C23 implications for C libraries
Date: Sun, 25 Sep 2022 23:33:22 -0400 [thread overview]
Message-ID: <20220926033322.GC9709@brightrain.aerifal.cx> (raw)
In-Reply-To: <20220924093106.41e53819@inria.fr>
On Sat, Sep 24, 2022 at 09:31:06AM +0200, Jₑₙₛ Gustedt wrote:
> enh,
>
> on Fri, 23 Sep 2022 16:52:53 -0700 you (enh <enh@google.com>) wrote:
>
> > On Fri, Sep 23, 2022 at 8:40 AM Jₑₙₛ Gustedt <jens.gustedt@inria.fr>
> > wrote:
> >
> > > enh,
> > >
> > > on Fri, 23 Sep 2022 08:28:52 -0700 you (enh <enh@google.com>) wrote:
> > >
> > > > since you asked for comments, it would have been even better to
> > > > have direct links to the relevant documents (such as
> > > > https://www.open-std.org/jtc1/sc22/WG14/www/docs/n2829.htm for the
> > > > assert() changes),
> > >
> > > yes, the idea is to add such a link when I manage to discuss the
> > > particular feature more in detail
> > >
> >
> > that...
>
> wow, that's pushy
>
> > > my hope is also still that we may have a diff-version of the C
> > > standard at some point in the nearer future, but it seems that the
> > > editors have problems with the tooling for that
> > >
> >
> > ...and that sound even better, yes --- but i always worry about "the
> > perfect is the enemy of the good". a 20% solution today is worth more
> > to me than a 100% solution a year from now :-)
>
> Much as musl, the C standard is a volunteer project. Instead of
> reclaiming things you should ask yourself how can you or your company
> help.
>
> As all volunteer work, this is best effort. WG14 would have a much
> better stand if more of the industry would inject real work force into
> the committee. Currently there seem only be two of the bigger players
> that have people there that substantially work on the C standard
> during their office hours. The others are mostly academics like myself
> and people working in their free time.
All that ^^^
next prev parent reply other threads:[~2022-09-26 3:33 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 [this message]
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
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=20220926033322.GC9709@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=enh@google.com \
--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).