Path: utzoo!attcan!uunet!ginosko!usc!ucla-cs!uci-ics!rfg
From: rfg@ics.uci.edu (Ronald Guilmette)
Newsgroups: comp.lang.c++
Subject: Re: Does C++ 2.0 Emit Following C Construct?
Message-ID: <1989Oct7.193756.1262@paris.ics.uci.edu>
Date: 7 Oct 89 19:37:56 GMT
References: <32793@cornell.UUCP> <6590285@hplsla.HP.COM>
Sender: news@paris.ics.uci.edu (Network News)
Reply-To: Ronald Guilmette <rfg@ics.uci.edu>
Organization: University of California, Irvine - Dept of ICS
Lines: 22

In article <6590285@hplsla.HP.COM> jima@hplsla.HP.COM (Jim Adcock) writes:
>
>...  I was assuming that if 2.0 wouldn't accept a 
>construct, it ought to be smart enough not to emit it either. 

One would hope so.  One would also hope that Cfront would be smart enough
to avoid emitting code that your native C compiler will subsequently choke
on.  Unfortunately, this is not always true.

Try this little gem (but first make sure that your CC script does *not*
invoke the GNU C compiler):

	int i;

	int main ()
	{

		i = sizeof (main);
		return 0;
	}

// rfg