Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.lang.c
Subject: Re:  int16, int32
Message-ID: <1167@umcp-cs.UUCP>
Date: Fri, 9-Aug-85 07:56:36 EDT
Article-I.D.: umcp-cs.1167
Posted: Fri Aug  9 07:56:36 1985
Date-Received: Mon, 12-Aug-85 02:41:36 EDT
References: <541@brl-tgr.ARPA>
Organization: U of Maryland, Computer Science Dept., College Park, MD
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.

I beg to differ: I tend to use "int" when 16 bits will suffice and
I'm not concerned with data space, and I think many others would do
the same, especially since the 4BSD Vax PCC compiler (and probably
many other compilers (SysV Vax PCC?)) won't put "register short"s
into registers.  (Someday, someone should fix that....)
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 4251)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@maryland