Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!cimshop!davidm From: cimshop!davidm@uunet.UU.NET (David S. Masterson) Newsgroups: comp.sys.amiga.programmer Subject: Re: C++ Message-ID: Date: 23 Apr 91 23:18:16 GMT References: <36711@ditka.Chicago.COM> <20860@cbmvax.commodore.com> Sender: davidm@cimshop.UUCP Distribution: comp Organization: Consilium Inc., Mountain View, California Lines: 50 In-reply-to: daveh@cbmvax.commodore.com's message of 22 Apr 91 22:29:11 GMT >>>>> On 22 Apr 91 22:29:11 GMT, daveh@cbmvax.commodore.com (Dave Haynie) said: Dave> In article <36711@ditka.Chicago.COM> comeau@csanta.attmail.com (Greg Dave> Comeau) writes: Greg> In article Greg> cimshop!davidm@uunet.UU.NET (David S. Masterson) writes: David> Lattice C++ was a port of AT&T C++ 1.2 compiler to the Amiga and, so, David> is just a translator rather than a direct to object file compiler. Greg> It's not "just a translator"! ;-) It does complete compiler duties Greg> (error checking, syntax checking, semantics of C++, etc) building Greg> internal trees looking nothing like C or C++. It just so happens that Greg> in the code generation phase it outputs C as its object code depending Greg> upon the C compiler only for the native object code generation. Dave> Sure sounds like the classical definition of "translator" to me. For Dave> those who haven't taken a compiler design course, you all should know Dave> that all compilers are also "translators". If a translator takes in Dave> some HLL, and spits out object code, it's a compiler. If not, it is Dave> some other kind of translator. Now, now. Greg was making the point that, in the case of C++ "translators", they spit object code. Its just that the object code is C. Now are you going to turn around and define object code? :-) David> Comeau Computing (718-945-0009) has recently announced a port of AT&T David> C++ 2.1 Greg> This is true. Dave> And that sounds like something I'm REAL interest in. I really want to Dave> program in C++, but gave up on Lattice C++ 1.0 for the most part, mainly Dave> because of its lack of source level debugging. All that crashing on Dave> syntax errors didn't help either. This is something that I haven't seen a "definitive" answer to, yet. What are the capabilities of source level debugging this C++ with a C compiler's source level debugger (CPR or SDB). I believe (correct me if I'm wrong) that you might have the capability to step through your code statement by statement, but it might be more difficult to find the value of a variable (unless you remember how name mangling works). -- ==================================================================== David Masterson Consilium, Inc. (415) 691-6311 640 Clyde Ct. uunet!cimshop!davidm Mtn. View, CA 94043 ==================================================================== "If someone thinks they know what I said, then I didn't say it!"