Path: csiph.com!news.swapon.de!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: Portable 16 bit binary integer write Date: Thu, 15 Sep 2016 18:35:44 -0700 Organization: None to speak of Lines: 18 Message-ID: References: <50a1e8f4-4fb3-4491-97d0-54768bf28685@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="945944de09706c9b4e29b53c9d2efdc2"; logging-data="24704"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+OZNuKq2lCvWqomn7znJkS" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:R1A7r8AJfvr6ffg+DZy4KhxS9Kc= sha1:ogkj7YHPHYrzKw21+Er7vrgbNfA= Xref: csiph.com comp.lang.c:93593 supercat@casperkitty.com writes: [...] > The authors of the C Standard have indicated in their rationale that they > would expect that commonplace implementations would process the above > function correctly. Should the fact that the Standard would allow an > implementation to do otherwise be taken as implying that a quality > implementation for a two's-complement platform *should* do so? You should start a blog so you can make these points without re-writing them every time. (Don't worry, this is the last time I'll do this.) -- 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"