From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] always use demangled name to set scope
Date: Fri, 13 Jun 2003 18:53:00 -0000 [thread overview]
Message-ID: <ro1d6hhzu4p.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20030613043834.GA24239@nevyn.them.org>
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
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.)
Namespace deduction is less important, I agree.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-06-13 18:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 22:26 David Carlton
2003-06-12 23:18 ` Daniel Jacobowitz
2003-06-13 1:01 ` David Carlton
2003-06-13 4:22 ` Daniel Jacobowitz
2003-06-13 4:28 ` David Carlton
2003-06-13 4:38 ` Daniel Jacobowitz
2003-06-13 18:53 ` David Carlton [this message]
2003-06-13 18:56 ` Daniel Jacobowitz
2003-06-13 19:01 ` David Carlton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ro1d6hhzu4p.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox