Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!tk
From: tk@moss.ATT.COM
Newsgroups: net.lang.c++
Subject: Re: C++ and sizeof
Message-ID: <1772@clyde.ATT.COM>
Date: Sun, 19-Oct-86 19:56:49 EDT
Article-I.D.: clyde.1772
Posted: Sun Oct 19 19:56:49 1986
Date-Received: Tue, 21-Oct-86 06:36:24 EDT
References: <3522@columbia.UUCP>
Sender: nuucp@clyde.ATT.COM
Reply-To: tk@moss.UUCP (Thomas Kirk)
Organization: AT&T Bell Laboratories, Whippany NJ
Lines: 10

In article <3522@columbia.UUCP> eppstein@garfield.columbia.edu (David Eppstein) writes:
>Is there a good reason why CC expands sizeof itself?  E.g. in
> ...
>why does the  sizeof(y)  become  8  and not  sizeof(struct x)?
>Is there some other use CC makes of the size that makes up for the
>resulting lack of portability?

What lack of portability? If you're counting on the C++ translator to produce
"portable C" as its output I think you'll have problems since cfront uses
machine dependent size and alignment information.