Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!sri-spam!ames!styx!lll-lcc!well!msudoc!umich!jtr485
From: jtr485@umich.UUCP
Newsgroups: comp.lang.c,comp.unix.wizards
Subject: Re: Time for 64-bit longs?
Message-ID: <65@umich.UUCP>
Date: Sat, 31-Jan-87 22:25:56 EST
Article-I.D.: umich.65
Posted: Sat Jan 31 22:25:56 1987
Date-Received: Tue, 3-Feb-87 20:50:16 EST
References: <848@epimass.UUCP> <291@mtxinu.UUCP>
Organization: EECS, University of Michigan
Lines: 12
Xref: watmath comp.lang.c:918 comp.unix.wizards:792

In article <291@mtxinu.UUCP>, ed@mtxinu.UUCP writes:
> >Has anyone bit the bullet and gone to 64-bit longs?
> 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.
NO!  Int does not have to be short or long.  It just has to be at least
as large as short and at least as small as long.  So you can have
8 bit short; 16 bit int; 32 bit long	/* some 68000 C compilers have this */
or
16 bit short; 32 bit int; 64 bit long	/* reasonable for a vax */
> Ed Gould                    mt Xinu, 2560 Ninth St., Berkeley, CA  94710  USA