Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!sri-spam!sri-unix!hplabs!decwrl!decvax!tektronix!uw-beaver!cornell!vax1!jsm
From: jsm@vax1.UUCP
Newsgroups: comp.lang.c,comp.unix.wizards
Subject: Re: Time for 64-bit longs?
Message-ID: <260@vax1.ccs.cornell.edu>
Date: Thu, 29-Jan-87 23:58:20 EST
Article-I.D.: vax1.260
Posted: Thu Jan 29 23:58:20 1987
Date-Received: Sat, 31-Jan-87 07:41:00 EST
References: <848@epimass.UUCP>
Reply-To: jsm@vax1.UUCP (Jon Meltzer)
Organization: Cornell Computer Services, Ithaca NY
Lines: 9
Xref: watmath comp.lang.c:890 comp.unix.wizards:759

In article <848@epimass.UUCP> jbuck@epimass.UUCP (Joe Buck) writes:
>Has anyone bit the bullet and gone to 64-bit longs?  I know Convex
>has a monstrosity called a "long long" that's 64 bits; they leave
>long as 32 bits, the same as int, apparently because it was too hard
>to change all the Berkeley code that assumes long == int.  But it
>seems the Vax architecture will soon require a 64-bit type at the
>high end.

And will the future 128-byte pointer be a "long long long" ?