From owner-freebsd-current  Mon Mar 10 14:48:07 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA04563
          for current-outgoing; Mon, 10 Mar 1997 14:48:07 -0800 (PST)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA04556
          for <current@freebsd.org>; Mon, 10 Mar 1997 14:48:03 -0800 (PST)
Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id OAA07326; Mon, 10 Mar 1997 14:46:52 -0800 (PST)
To: Terry Lambert <terry@lambert.org>
cc: current@freebsd.org
Subject: Re: 2 questions about C++ support in 2.2 
In-reply-to: Your message of "Mon, 10 Mar 1997 15:31:08 MST."
             <199703102231.PAA23772@phaeton.artisoft.com> 
Date: Mon, 10 Mar 1997 14:46:52 -0800
Message-ID: <7322.858034012@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> I defer to Warner for a better analysis...  (ducks and runs).

I was sort of hoping that Warner might help me solve it, yes.. :)

> > 2. Shouldn't these messages demange the symbol first, so you don't
> >    have to hassle with c++filt?  I thought we were here once before
> > ..
> 
> You'd have to demange it for attribution of paramters, since you
> could have a conflict declaration, and if you demanged it to not
> show any attribution of paramters or return value, you'd never
> figure out where the hell you screwed up.  8-).

I like how my own typo (demange vs demangle) was not only replicated
multiple times in my own posting (I guess my eye just saw the previous
instance and cloned it) but into Terry's reply as well. :-)

Either that or Terry, like me, thought that "demange" was actually a
far more descriptive metaphor for c++ symbol munging.  If ever
there was a language with a serious case of the mange, it's C++.

					Jordan