Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!sri-unix!sri-spam!mordor!lll-lcc!unisoft!mtxinu!ed
From: ed@mtxinu.UUCP
Newsgroups: comp.lang.c,comp.unix.wizards
Subject: Re: Time for 64-bit longs?
Message-ID: <291@mtxinu.UUCP>
Date: Thu, 29-Jan-87 12:46:33 EST
Article-I.D.: mtxinu.291
Posted: Thu Jan 29 12:46:33 1987
Date-Received: Sat, 31-Jan-87 04:39:50 EST
References: <848@epimass.UUCP>
Reply-To: ed@mtxinu.UUCP (Ed Gould)
Organization: mt Xinu, Berkeley, CA
Lines: 19
Xref: watmath comp.lang.c:885 comp.unix.wizards:752

>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.

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.

Other people have used the "long long" hack, too.

-- 
Ed Gould                    mt Xinu, 2560 Ninth St., Berkeley, CA  94710  USA
{ucbvax,decvax}!mtxinu!ed   +1 415 644 0146

"A man of quality is not threatened by a woman of equality."