Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: 'C' Standards <was: Re: Passing (char *) NULL to printf to match %s>
Message-ID: <6295@brl-smoke.ARPA>
Date: Wed, 31-Dec-69 18:59:59 EDT
Article-I.D.: brl-smok.6295
Posted: Wed Dec 31 18:59:59 1969
Date-Received: Sat, 22-Aug-87 06:15:05 EDT
References: <166@qetzal.UUCP> <157@hobbes.UUCP> <875@bsu-cs.UUCP> <1219@cognos.UUCP> <25173@sun.uucp> <298@apex.UUCP> <2163@xanth.UUCP> <1112@laidbak.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 14

In article <1112@laidbak.UUCP> guardian@laidbak.UUCP writes:
>Let chars be 8 bits, ints be 2*8, longs be 4*8, doubles be 8*8

Get real -- C has to fit available computers, not the other way
around.  In fact, (int) CANNOT be as small as you suggest in any
process address space > 15 bits without causing problems.  It
should not matter for the vast majority of applications just how
many bits are in a data type, so long as there are enough; the
remaining applications are trying to do something non-portable
anyway.

If you're going to suggest changes to C, please make them
realistic.  There is enough traffic in this group already
without starting utterly irrelevant discussions.