From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@kealia.com>
Cc: Michael Elizabeth Chastain <mec@shout.net>,
gdb-patches@sources.redhat.com
Subject: Re: [patch/testsuite] gdb.c++/classes.exp: add another ptype pattern
Date: Wed, 02 Jul 2003 18:33:00 -0000 [thread overview]
Message-ID: <20030702183257.GA8828@nevyn.them.org> (raw)
In-Reply-To: <yf2of0cg8ly.fsf@hawaii.kealia.com>
On Wed, Jul 02, 2003 at 10:07:53AM -0700, David Carlton wrote:
> On Wed, 2 Jul 2003 12:49:20 -0400, Michael Elizabeth Chastain <mec@shout.net> said:
>
> > The big stab for ClassWithEnum is the same, but the stab for the
> > nested enum changed from 'PrivEnum' to 'ClassWithEnum::PrivEnum'.
> > The hypothetical case has came to life. Argh!
>
> > Is it good for us that gcc 3.3 and later versions output
> > 'ClassWithEnum::PrivEnum'? Or should I file a bug report against
> > gcc and ask them to put it back to just plain 'PrivEnum'?
>
> It might be a good idea as part of a larger change (to the names of
> all nested classes). It's probably not a great idea if the change
> only involves enums nested with classes, though others might disagree
> with me on that.
>
> What certainly isn't a good idea is that it's changed and nobody has
> bothered to discuss this with us. Maybe a good course of action would
> be to post to gcc@ asking about it.
Eh, I believe Kevin B. did it:
2002-05-22 Kevin Buettner <kevinb@redhat.com>
* dbxout.c (dbxout_class_name_qualifiers): New function.
(dbxout_symbol): Output class/struct qualifiers for a .stabs entry.
Ask him about it instead of blaming GCC...
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-07-02 18:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 16:49 Michael Elizabeth Chastain
2003-07-02 17:07 ` David Carlton
2003-07-02 18:33 ` Daniel Jacobowitz [this message]
2003-07-02 19:02 ` Kevin Buettner
2003-07-02 19:19 ` David Carlton
2003-07-02 20:47 ` Kevin Buettner
-- strict thread matches above, loose matches on Subject: below --
2003-07-02 21:33 Michael Elizabeth Chastain
2003-07-02 20:58 Michael Elizabeth Chastain
2003-07-02 19:11 Michael Elizabeth Chastain
2003-07-02 17:28 Michael Elizabeth Chastain
2003-07-02 16:09 Michael Elizabeth Chastain
2003-07-02 16:29 ` David Carlton
2003-07-02 16:38 ` Daniel Jacobowitz
2003-07-02 16:01 Michael Elizabeth Chastain
2003-07-02 15:39 Michael Elizabeth Chastain
2003-07-02 15:51 ` Daniel Jacobowitz
2003-07-02 15:52 ` 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=20030702183257.GA8828@nevyn.them.org \
--to=drow@mvista.com \
--cc=carlton@kealia.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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