Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!sdrc!gefrank From: gefrank@sdrc.COM (Frank Glandorf) Newsgroups: comp.sys.amiga.programmer Subject: Re: REVIEW: Comeau C++ compiler Summary: Source code debuggers are important Message-ID: <929@sdrc.COM> Date: 1 May 91 17:25:27 GMT References: <4670@orbit.cts.com> <37498@ditka.Chicago.COM> <41769@cup.portal.com> <37918@ditka.Chicago.COM> Organization: SDRC, Cincinnati Lines: 36 In article <37918@ditka.Chicago.COM>, comeau@ditka.Chicago.COM (Greg Comeau) writes: > 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) Source code debuggers are important. If the source code and target language are close then debugging the target language is not difficult. C source debuggers work well with translators like lex and yacc. However Ratfor is sufficiently different from FORTRAN that I have trouble debugging it. Debugging assembler from C source is not worth the effort for the applications that I develop. > Line number and source file information is retained and that is simply > accepted by the C compiler. There is no special trick involved. Hmm. Sounds like the "#line" directive. This is really more useful for diagnostic messages than source code debugging. > >Could you post a file which contains some source code,... > I don't see what that would accomplish. I too would like to see the generated C code. If the C++ source and generated C are close then I might buy Comeau C++ otherwise I'll wait for a C++ that has a source code debugger. > - 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 -Frank