Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!samsung!sdd.hp.com!usc!pollux.usc.edu!kjh
From: kjh@pollux.usc.edu (Kenneth J. Hendrickson)
Newsgroups: comp.os.minix
Subject: Re: use only short and long (not int) in struct message
Message-ID: <29226@usc>
Date: 9 Jan 91 20:38:51 GMT
References: <41145@nigel.ee.udel.edu>
Sender: news@usc
Organization: EE-Systems, USC, Los Angeles
Lines: 17
Nntp-Posting-Host: pollux.usc.edu

In article <41145@nigel.ee.udel.edu> burgess%creek.decnet@hqhsd.brooks.af.mil (CREEK::BURGESS) writes:
>  Wasn't the original definition of "short" and "long" from K&R explicit?

No.  From K&R 2nd edition, page 36:

		The intent is that short and long should provide
	different lengths where practical; int will normally be the
	natural size for a particular machine.  short is often 16 bits,
	long 32 bits, and int either 16 or 32 bits.  Each compiler is
	free to choose appropriate sizes for its own hardware, subject
	to the restriction that shorts and ints are at least 16 bits,
	longs are at least 32 bits, and short is no longer than int,
	which is no longer than long.

-- 
favourite oxymorons:   student athlete, military justice, mercy killing
Ken Hendrickson N8DGN/6       kjh@usc.edu      ...!uunet!usc!pollux!kjh