[rfa] always use demangled name to set scope

[Daniel Jacobowitz]

On Fri, Jun 13, 2003 at 11:53:42AM -0700, David Carlton wrote:
> On Fri, 13 Jun 2003 00:38:34 -0400, Daniel Jacobowitz <drow@mvista.com> said:
> > On Thu, Jun 12, 2003 at 09:28:13PM -0700, David Carlton wrote:
> 
> >> Yeah, but we need DW_TAG_namespace to do [nested type deduction],
> >> and a version of GCC providing that probably won't be released
> >> until next calendar year.  I certainly don't use demangled names to
> >> do nested type deduction if we have DW_TAG_namespace, but I do
> >> think it will be important for the next two or three years.
> 
> > That's namespace deduction.  Nested type deduction is a slightly
> > different story - the principle is the same but we already have all
> > the information we need.
> 
> Not if the type is nested inside a namespace.  If your code is full of

Violent agreement again.  I'm using the words differently from you; I
was strictly speaking about
class C {
  class D {
    ..
  };
};

>   namespace N {
>     class C {
>       ...
>     };
>   }
> 
> then, as far as I can tell, you can't tell that C is really N::C
> without either DW_TAG_namespace or demangled names.  And if you think
> it's C, then users get confused if they refer to it as N::C and
> nothing happens, and you get constant RTTI warnings when printing out
> stuff.  (Which, besides being annoying, make ddd impossible to use,
> which matters to some people.)

Yes, all definitely true.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer