Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site rlgvax.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!teddy!panda!talcott!harvard!seismo!rlgvax!guy From: guy@rlgvax.UUCP (Guy Harris) Newsgroups: net.unix-wizards,net.lang.c Subject: Re: integer types, sys calls, and stdio Message-ID: <377@rlgvax.UUCP> Date: Sun, 20-Jan-85 16:42:34 EST Article-I.D.: rlgvax.377 Posted: Sun Jan 20 16:42:34 1985 Date-Received: Tue, 22-Jan-85 06:31:00 EST References: <1997@mordor.UUCP> <270@mtxinu.UUCP> Distribution: net Organization: CCI Office Systems Group, Reston, VA Lines: 16 Xref: watmath net.unix-wizards:11656 net.lang.c:3991 > > One final recourse for us would be to admit defeat, change "long" > > to 36-bits, and hack in a "long long" type for 72-bit integers. > > Please DO! The definition of C calls for *two* lengths of integers: > "short int" and "long int". "int" alone may be defined as one or the > other. Actually, the C reference manual calls for up to *three* lengths of integers: "short int", "int", and "long int"; any of them may be equivalent to the other as long as sizeof(short int) <= sizeof(int) <= sizeof(long int). In practice, it may cause problems if "int" isn't the same as any of the other two, but that's because of historical practice, not because of the "specification" of the language. Guy Harris {seismo,ihnp4,allegra}!rlgvax!guy