From: Florian Weimer <fweimer@redhat.com>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: C Annex K safe C functions
Date: Mon, 04 Mar 2019 09:09:31 +0100 [thread overview]
Message-ID: <87wolfm56s.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20190227163420.GU23599@brightrain.aerifal.cx> (Rich Felker's message of "Wed, 27 Feb 2019 11:34:20 -0500")
* Rich Felker:
> 5. Expanding on the topic of FUD/misinformation, both the introduction
> of the original *_s functions, and lobbying for their inclusion in the
> standard (which eventually reached the compromise of just putting them
> in an Annex), was not about improving the C language or making useful
> tools for programmers, but about introducing incompatibility and
> fragmentation to the language/standard with the goal of undermining
> it. The company that introduced it produces a product that is not
> compatible with the C language as specified and does not even aim to
> be, but aims to give the impression of being a C implementation (it's
> mainly a C++ implementation, though likely not conforming to that
> standard either).
Does this really reflect history? I thought that Annex K was submitted
for standardization well after the vendor in question withdrew from the
ISO process.
> It's my position, and I believe it's shared by many others in the musl
> community and C language communities, that parties not interested in
> implementing or using the standard should not try to influence its
> direction, and that this kind of behavior should not be rewarded by
> playing along with it, but that it should be shunned as long as doing
> so is practical.
My impression is that compiler vendors and large-scale users are
generally not well-represented in the ISO process anyway. If true, your
requirement, while looking completely reasonable, would effectively halt
evolution of the standard.
Thanks,
Florian
next prev parent reply other threads:[~2019-03-04 8:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 3:30 Jonny Grant
2019-02-27 10:50 ` Szabolcs Nagy
2019-03-04 4:24 ` Jonny Grant
2019-03-04 6:40 ` A. Wilcox
2019-03-04 15:14 ` Rich Felker
2019-02-27 13:11 ` Rich Felker
2019-02-27 16:34 ` Rich Felker
2019-03-04 8:09 ` Florian Weimer [this message]
2019-03-05 13:19 ` Szabolcs Nagy
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=87wolfm56s.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=dalias@libc.org \
--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).