Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!unixhub!ditka!comeau
From: comeau@ditka.Chicago.COM (Greg Comeau)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: REVIEW:  Comeau C++ compiler
Keywords: programming, language, C++, compiler
Message-ID: <37044@ditka.Chicago.COM>
Date: 18 Apr 91 15:00:44 GMT
References: <1991Apr10.051104.25326@menudo.uh.edu> <36748@ditka.Chicago.COM> <1991Apr15.170545.14190@jato.jpl.nasa.gov>
Sender: comeau@ditka.chicago.com (Greg Comeau)
Reply-To: comeau@csanta.attmail.com (Greg Comeau)
Organization: Comeau Computing
Lines: 27

In article <1991Apr15.170545.14190@jato.jpl.nasa.gov> jdickson@jato.Jpl.Nasa.Gov (Jeff Dickson) writes:
>In article <36748@ditka.Chicago.COM> comeau@csanta.attmail.com (Greg Comeau) writes:
>>since we are requiring that you have a C
>>compiler, and since each C compiler is slightly different, if we literally
>
>	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.
>

Like it says, we currently require you to have a C compiler.  Comeau C++
DOES NOT rewrite your C++ source into plain'ol C though.  It does full
compilation (syntax, semantic, error, type, etc checking, analysis, etc)
and decides in it's code generation phase to output C based on it internal
compiler trees (which look nothing like C or C++ BTW).  So, since the C has
the includes already, it would be redundant for us to re-supply them.

Only in cases where things have "gone wrong" will we supply an include file
and/or a patch to one.

- 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