Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: Something C might need Date: Sun, 24 Sep 2017 12:03:30 -0700 Organization: None to speak of Lines: 36 Message-ID: References: <1cc86992-d71e-42b9-818f-f883b78e79ce@googlegroups.com> <7ac3b44a-b838-4462-88c8-adcd77d61ce1@googlegroups.com> <87wp4p4sej.fsf@bsb.me.uk> <87o9q14343.fsf@bsb.me.uk> <74c104d0-10ea-43ac-a302-3685560de3ce@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader02.eternal-september.org; posting-host="f340375e532714dc24c747dfdddc9b11"; logging-data="15024"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+iO6pNvXJ7wyxJW6McC6JW" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:7cN15zxeVU2KGr4MjfT4S4Kf2RU= sha1:A83tJSns0GRuNRuqRV4gErv0Gw8= Xref: csiph.com comp.lang.c:120235 David Kleinecke writes: [...] > The standard (C89 if they differ) allows the integer types to have > a wide variety of implementations. I am proposing one possible > system of implementations. I believe I have not proposed anything > the standards forbid. And I offered a reason - which I feel is the > most natural one - for why I made such a proposal. You have proposed eliminating long long, which is of course forbidden by C99 and C11 (which replaced C89/C90). And you have said you "insist" on "long" meaning twice and "short" meaning half. If you meant that that's your personal preference, you should have said so. > How and why all the other current ways to handle the integer types > were proposed is relevant only in comparison with my proposal. > > And I do not assume the standard library. In the sense that I do > not treat it as in any way privileged or a priori obvious. But it > is available as any other library might be. "stdio" is very > useful. The standard library is an integral part of the C standard (though freestanding implementations are not required to provide most of it). What is the intended context for your proposal? Do you want all implementations to support it? Do you want it to be required by a future standard? -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"