Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!caen!uwm.edu!linac!unixhub!ditka!comeau
From: comeau@ditka.Chicago.COM (Greg Comeau)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: REVIEW:  Comeau C++ compiler
Message-ID: <37918@ditka.Chicago.COM>
Date: 30 Apr 91 20:50:57 GMT
References: <4670@orbit.cts.com> <37498@ditka.Chicago.COM> <41769@cup.portal.com>
Sender: comeau@ditka.Chicago.COM (Greg Comeau)
Reply-To: comeau@csanta.attmail.com (Greg Comeau)
Organization: Comeau Computing
Lines: 28

In article <41769@cup.portal.com> Lee_Robert_Willis@cup.portal.com writes:
>I'm very curious about how and to what extent SAS's CPR can be used
>to debug Comeau's C++ code.  (A debugger is a _big_ issue.  I
>wasn't considering buying your compiler until you mentioned that C 
>debuggers could be used)

Line number and source file information is retained and that is simply
accepted by the C compiler.  There is no special trick involved.

>Could you post a file which contains some source code, and the
>compiled executable (compiled with debug) so those of us with
>debuggers could try it out for ourselves? 

I don't see what that would accomplish.  It is my understanding that
others here on the net have Comeau C++ and they are not disputing
what I am saying.  Since information about the original C++ source
file is retained, the debug information points to the C++ source (as in most
of this compilation process, the .c is truly only as a medium).  Since the
debug information is also know to the debugger, doing, say, a single step,
is not a problem.


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