Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!asuvax!ukma!usenet.ins.cwru.edu!ysub!psuvm!blekul11!ghgaqz4
From: GHGAQZ4@cc1.kuleuven.ac.be
Newsgroups: comp.sys.amiga.programmer
Subject: Re: REVIEW: Comeau C++ compiler
Message-ID: <91113.094717GHGAQZ4@cc1.kuleuven.ac.be>
Date: 23 Apr 91 09:45:17 GMT
References: <4670@orbit.cts.com>
Organization: K.U.Leuven - Academic Computing Center
Lines: 19

>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?

I hope Lattice is NEVER going to do that (except when they make it optional
ofcourse) because this approach is slow (not that Lattice is very fast at
this moment but it would be worse with compilation to assembly instead of
object code). And there is still another reason that I don't want that :
Lattice ASM is about the slowest assembler I've ever seen. If you'd had
to assemble after each compile session your productivity level would go
below zero I think.

   Jorrit Tyberghein