Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!sri-spam!ames!ucbcad!ucbvax!cartan!brahms.Berkeley.EDU!ballou
From: ballou@brahms.Berkeley.EDU.UUCP
Newsgroups: comp.lang.c,comp.unix.wizards
Subject: Re: Time for 64-bit longs?
Message-ID: <856@cartan.Berkeley.EDU>
Date: Fri, 30-Jan-87 17:19:35 EST
Article-I.D.: cartan.856
Posted: Fri Jan 30 17:19:35 1987
Date-Received: Sat, 31-Jan-87 09:25:36 EST
References: <848@epimass.UUCP> <291@mtxinu.UUCP>
Sender: daemon@cartan.Berkeley.EDU
Reply-To: ballou@brahms.Berkeley.EDU (Kenneth R. Ballou)
Organization: Math Dept. UC Berkeley
Lines: 24
Xref: watmath comp.lang.c:894 comp.unix.wizards:764

In article <291@mtxinu.UUCP> ed@mtxinu.UUCP (Ed Gould) writes:
>The problem is not that the VAX code assumes int == long (it often
>does make that assumption, but those are bugs) but that C defines
>only two sizes of integer: long and short.  Int may be either,
>depending on the implementation, but it must be one or the other.

	WRONG!

	K&R, pp. 182-3:

		Up to three sizes of integer, declared short int,
	int, and long int, are available.  Longer integers provide
	no less storage than shorter ones, but the implementation
	may make either short integers, or long integers, or both
	be equivalent to plain integers.

I don't see anything there that requires int be the same size as one of
short and long.

--------
Kenneth R. Ballou			ARPA:  ballou@brahms.berkeley.edu
Department of Mathematics		UUCP:  ...!ucbvax!brahms!ballou
University of California
Berkeley, California  94720