Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!ncar!gatech!usenet.ins.cwru.edu!ncoast!allbery
From: allbery@NCoast.ORG (Brandon S. Allbery KB8JRR/AA)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Debugging C++
Message-ID: <1991May7.000209.22888@NCoast.ORG>
Date: 7 May 91 00:02:09 GMT
References: <42022@cup.portal.com>
Reply-To: allbery@ncoast.ORG (Brandon S. Allbery KB8JRR/AA)
Followup-To: comp.sys.amiga.programmer
Organization: North Coast Public Access Un*x (ncoast)
Lines: 30

As quoted from <42022@cup.portal.com> by Lee_Robert_Willis@cup.portal.com:
+---------------
| Greg Comeau> Comeau C++ comes with a utility we call c++filt, c++filt.CC, or
| Greg Comeau> comofilt depending upon the port (don't ask we why haven't
| Greg Comeau> standardized the name please) that supports just such a
| Greg Comeau> demangling capability.
| 
| Why would one need a name-demangler if the debugger shows C++ source code?
+---------------

The source code may well be shown from the C++ file, but the stack traceback
and other debugger calls that don't hit the C++ source file will be based on
the C symbols.

This is a standard problem with preprocessor-based languages (you can even get
it using C if you are sufficiently devious with your #defines).  The problem
is, writing a native C++ compiler takes a lot more work and therefore presents
the opportunity for a lot more compiler bugs.  And it's almost always more
expensive (the "almost" mainly because of G++).

It's a tradeoff, of course.  If possible, your best course of action is to try
it out first (both native C++ compilers and cfront-based ones) --- and to
check with your pocketbook before buying.

++Brandon
-- 
Me: Brandon S. Allbery			  Ham: KB8JRR/AA  10m,6m,2m,220,440,1.2
Internet: allbery@NCoast.ORG		       (restricted HF at present)
Delphi: ALLBERY				 AMPR: kb8jrr.AmPR.ORG [44.70.4.88]
uunet!usenet.ins.cwru.edu!ncoast!allbery       KB8JRR @ WA8BXN.OH