Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site sdcrdcf.UUCP
Path: utzoo!linus!decvax!tektronix!hplabs!sdcrdcf!doon
From: doon@sdcrdcf.UUCP (Harry W. Reed)
Newsgroups: net.lang.c
Subject: Re:  int16, int32
Message-ID: <2251@sdcrdcf.UUCP>
Date: Thu, 15-Aug-85 11:32:52 EDT
Article-I.D.: sdcrdcf.2251
Posted: Thu Aug 15 11:32:52 1985
Date-Received: Mon, 19-Aug-85 22:28:31 EDT
References: <541@brl-tgr.ARPA> <1167@umcp-cs.UUCP> <384@uwmcsd1.UUCP> <2620@sun.uucp>
Reply-To: doon@sdcrdcf.UUCP (Harry W. Reed)
Organization: System Development Corp. R+D, Santa Monica
Lines: 21
Summary: 

In article <2620@sun.uucp> guy@sun.uucp (Guy Harris) writes:
>> >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

Hi:
	The Harris H800 (etc) implementation of 'C' uses 24-bit integers.
I've worked on a Harris for about 2 years and I must say that it has a 
VERY NASTY machine architecture. Gimme a VAX or a 32000 any day!!!


	Harry Reed