Path: csiph.com!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: iso646.h Date: Mon, 22 Jan 2024 13:22:41 -0800 Organization: None to speak of Lines: 20 Message-ID: <87plxt9i72.fsf@nosuchdomain.example.com> References: <8FwrN.323724$p%Mb.66745@fx15.iad> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: dont-email.me; posting-host="9cd31264156fc70cf12828e27041ba36"; logging-data="960616"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/cR63RhtXNozBsDZ/JujKO" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) Cancel-Lock: sha1:lxJFH3RTXQHpCwKpUko+Wi0IseA= sha1:NamH2aczCVtJWlVAg9AqLXkiSP0= Xref: csiph.com comp.lang.c:380640 Lawrence D'Oliveiro writes: > On Mon, 22 Jan 2024 16:24:36 GMT, Scott Lurndal wrote: >> Although it was available before 1999 - the SVR4 C compilation System >> (CCS) had an iso6[4]6.h header file in the early 90's. > > By the way, why is it called “iso646.h”? ISO 646 is the ISO standard for the ASCII 7-bit character set. The header's original intent was to make C programming easier on systems that don't support all ASCII characters, either because they use EBCDIC or because they use 7-bit character sets that replace some puncutation characters with, for example, accented letters. As for "and" being more readable than "&&", that's not necessarily the case for people who are accustomed to reading C code. -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com Working, but not speaking, for Medtronic void Void(void) { Void(); } /* The recursive call of the void */