Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!sdd.hp.com!spool.mu.edu!cs.umn.edu!kksys!orbit!pnet51!chucks
From: chucks@pnet51.orb.mn.org (Erik Funkenbusch)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: REVIEW:  Comeau C++ compiler
Message-ID: <4670@orbit.cts.com>
Date: 22 Apr 91 06:17:22 GMT
Sender: news@orbit.cts.com
Organization: People-Net [pnet51], Minneapolis, MN.
Lines: 18

tron1@tronsbox.xei.com (Kenneth Jamieson) writes:
>	The "official" AT&T Cfront program is what defines the C++
>standard. That program takes C++ and generates C.
>

So then, the new lattice C++ (from what i've heard) will compile directly to
object modules.  this means then that the lattice compiler will not be
standard?  I've ALWAYS disliked the fact that with lattice you had to
dis-assemble an object module to see the assembly as well.  to me the perfect
C++ would compile to C, then from C to assembly, and then assemble the
assembly, of course allowing anywhere in between to stop and examine any
stage.  the Manx C compiler does this quite well, even embeds the C source
into the assembly as comments if you like.  Would anyone else like a C++
compiler to do this?

UUCP: {amdahl!tcnet, crash}!orbit!pnet51!chucks
ARPA: crash!orbit!pnet51!chucks@nosc.mil
INET: chucks@pnet51.orb.mn.org