Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!ncrlnk!ncr-sd!hp-sdd!hp-pcd!hplsla!jima
From: jima@hplsla.HP.COM (Jim Adcock)
Newsgroups: comp.lang.c++
Subject: Re: Does C++ 2.0 Emit Following C Construct?
Message-ID: <6590285@hplsla.HP.COM>
Date: 6 Oct 89 19:02:31 GMT
References: <32793@cornell.UUCP>
Organization: HP Lake Stevens, WA
Lines: 13

>Perhaps I didn't make the problem clear enough. It was the 1.2
>C++ compiler that emitted this code -- NOT me. All I was doing
>was writing some standard matrix/vector stuff and I found
>that the C code emitted contained these &f() constructs -- the original
>C++ code had nothing resembling them!

>So the 1.2 compiler emits bad C code. Original q: does the 2.0 compiler
>ever do this?

According to Shankar, no.  I was assuming that if 2.0 wouldn't accept a 
construct, it ought to be smart enough not to emit it either.  So
both by practical experience, and my indirect test, the answer seems to
be that 2.0 has fixed this.