Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!jato!jdickson
From: jdickson@jato.jpl.nasa.gov (Jeff Dickson)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: REVIEW:  Comeau C++ compiler
Keywords: programming, language, C++, compiler
Message-ID: <1991Apr15.170545.14190@jato.jpl.nasa.gov>
Date: 15 Apr 91 17:05:45 GMT
References: <1991Apr10.051104.25326@menudo.uh.edu> <36748@ditka.Chicago.COM>
Reply-To: jdickson@jato.Jpl.Nasa.Gov (Jeff Dickson)
Organization: Jet Propulsion Laboratory, Pasadena, CA
Lines: 27

In article <36748@ditka.Chicago.COM> comeau@csanta.attmail.com (Greg Comeau) writes:
>In article <1991Apr10.051104.25326@menudo.uh.edu> tron1@tronsbox.xei.com (Kenneth Jamieson) writes:
>
>>5) Run the "include" program. You have to do this once.  Comeau does NOT
>>distribute a full set of header files.  This program will take your existing
>>C header files and "C++"-ize them.
>
>It's hard to tell whether you consider this good or bad!  We think it
>good as our premise is that since we are requiring that you have a C
>compiler, and since each C compiler is slightly different, if we literally
>use what the C vendor supplies, little, if any, idiosyncrasies will crop
>up.  Once 'include' is run, that's it, and you never need to worry about it
>until you upgrade and/or change your C compiler.  Plus the C++ header and
>C headers can co-exist with no problem.

	I am confused. Does the C++ compiler rewrite your C++ source code into
plain'ol C and use your old 'C' compiler to compile it or is it that it was too
costly (whatever) to include your own includes? I don't understand how any
idiosyncrasies could crop up if your old compiler is not being used.

>
>-- Greg
>-- 
>	 Comeau Computing, 91-34 120th Street, Richmond Hill, NY, 11418
>                            Producers of Comeau C++
>          Here:attmail.com!csanta!comeau / BIX:comeau / CIS:72331,3421
>                     Voice:718-945-0009 / Fax:718-441-2310