Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 SMI; site sun.uucp
Path: utzoo!linus!philabs!cmcl2!seismo!harvard!talcott!panda!genrad!decvax!decwrl!sun!guy
From: guy@sun.uucp (Guy Harris)
Newsgroups: net.lang.c
Subject: Re:  int16, int32
Message-ID: <2620@sun.uucp>
Date: Tue, 13-Aug-85 02:48:32 EDT
Article-I.D.: sun.2620
Posted: Tue Aug 13 02:48:32 1985
Date-Received: Thu, 15-Aug-85 08:19:54 EDT
References: <541@brl-tgr.ARPA> <1167@umcp-cs.UUCP> <384@uwmcsd1.UUCP>
Organization: Sun Microsystems, Inc.
Lines: 12

> >In any case, most experienced C programmers will use "short" when 16
> >bits is known to suffice and "long" when 32 bits are needed.
> 
> (Mention of Sperry 1100 C with 18-bit "short"s and 36-bit "long"s).

In this case the above assumption is still reasonably good; what's two bits
between friends?  (Besides, what would $.25 buy you these days? :-))  24-bit
machines are trickier; 12 bits is too short for "short" (PDP-8 enthusiasts
nonwithstanding) and 48 bits is a bit long for a "long".  (Anybody know what
the Harris (no relation) 24-bit/48-bit machines' C implementations use?)

	Guy Harris