mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: C Annex K safe C functions
Date: Tue, 5 Mar 2019 14:19:42 +0100	[thread overview]
Message-ID: <20190305131942.GA26605@port70.net> (raw)
In-Reply-To: <87wolfm56s.fsf@oldenburg2.str.redhat.com>

* Florian Weimer <fweimer@redhat.com> [2019-03-04 09:09:31 +0100]:
> * 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.

well microsoft did lobby for the _s functions originally,
the msvc library team is likely responsible for the concept.
it turned into tr 24731 and eventually annex k in c11,
by that time microsoft may not have much to do with it.

one can dig through wg14 to see how it evolved.

initial work:
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1007.pdf
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1031.pdf
a tr 24731 meeting (ms is still involved):
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1129.pdf
some tr 24731 drafts:
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1088.pdf
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1146.pdf
austing group comments:
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1106.txt
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1160.pdf
responses:
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1118.htm
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1174.pdf
tr 24731 rationale:
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1173.pdf
c1x inclusion:
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1350.htm
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1394.pdf



      reply	other threads:[~2019-03-05 13:19 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
2019-03-05 13:19       ` Szabolcs Nagy [this message]

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=20190305131942.GA26605@port70.net \
    --to=nsz@port70.net \
    --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).