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: Fri, 22 Sep 2017 18:20:21 -0700 Organization: None to speak of Lines: 16 Message-ID: References: <1cc86992-d71e-42b9-818f-f883b78e79ce@googlegroups.com> <7ac3b44a-b838-4462-88c8-adcd77d61ce1@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader02.eternal-september.org; posting-host="04a59581cee8bc27b4414e17aac7cecf"; logging-data="8795"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/3HrKyPGAXz7V7lMT0A1D+" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:Zy669WiNxIJ2+se5C+KMjgdEZ9E= sha1:HvWWOIWzNywEQC1FEdqtx9vPwtk= Xref: csiph.com comp.lang.c:120178 David Kleinecke writes: [...] > Assuming the hardware arithmetic is 64-bit then I think it > would be best to have "short" be 32-bit, char 8-bit and > 16-bit "long char". "Wide char" would be more standard but > why introduce a new keyword. "Short short" for 16-bit would > be in the spirit of "long long" (which I assume no longer > would exist). How much existing code do you want to break? -- 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"