Xref: utzoo comp.lang.c++:13163 comp.lang.c:38883
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uwm.edu!ux1.cso.uiuc.edu!phil
From: phil@ux1.cso.uiuc.edu (Phil Howard KA9WGN)
Newsgroups: comp.lang.c++,comp.lang.c
Subject: Re: 64 bit architectures and C/C++
Message-ID: <1991May1.011248.24830@ux1.cso.uiuc.edu>
Date: 1 May 91 01:12:48 GMT
References: <168@shasta.Stanford.EDU> <6157@trantor.harris-atd.com>
Organization: University of Illinois at Urbana
Lines: 25

mvm@jedi.harris-atd.com (Matt Mahoney) writes:

>When I need to specify bits, I'm usually forced to make the 
>following assumptions:

>	char	8 bits
>	short	16 bits
>	long	32 bits

>since this is true on most machines.  Anything else would probably break
>a lot of code.

What would break if you did:

	char	8 bits
	short	16 bits
	int	32 bits
	long	64 bits

where any pointer or pointer difference would fit in 32 bits?
-- 
 /***************************************************************************\
/ Phil Howard -- KA9WGN -- phil@ux1.cso.uiuc.edu   |  Guns don't aim guns at  \
\ Lietuva laisva -- Brivu Latviju -- Eesti vabaks  |  people; CRIMINALS do!!  /
 \***************************************************************************/