Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site psivax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!harvard!talcott!panda!genrad!decvax!ittvax!dcdwest!sdcsvax!sdcrdcf!psivax!friesen
From: friesen@psivax.UUCP (Stanley Friesen)
Newsgroups: net.lang.c
Subject: Re: SIZEOF
Message-ID: <284@psivax.UUCP>
Date: Tue, 29-Jan-85 14:13:37 EST
Article-I.D.: psivax.284
Posted: Tue Jan 29 14:13:37 1985
Date-Received: Sat, 2-Feb-85 09:05:02 EST
References: <347@ecr.UUCP> <351@ecr.UUCP>
Reply-To: friesen@psivax.UUCP (Stanley friesen)
Organization: Pacesetter Systems Inc., Sylmar, CA
Lines: 22
Summary: 

In article <351@ecr.UUCP> quenton@ecr.UUCP (Dennis Smith) writes:
>It might also be noted, although I have had no experience with them,
>some compilers for certain older generations of computers, generate
>pointers of differing sizes.  This occurs when the machine is not
>byte addressable, so that a pointer to a word aligned item might
>be "n" bits long, but a pointer to a character must point to the
>word and also indicate which character within the word.
>This would make the even more disastrous situation of
>  sizeof(char *) != sizeof(int *)
>making the defintion of something like NULL even more incomprehensible.

	And not only "older" computers, the current Honeywell
mainframe has an architecture which works like this.  Of course
that is because they decided to maintain code compatibility with
their old 600 series from the mid-60s.
-- 

				Sarima (Stanley Friesen)

{trwrb|allegra|cbosgd|hplabs|ihnp4|aero!uscvax!akgua}!sdcrdcf!psivax!friesen
 or
quad1!psivax!friesen