From: David Carlton <carlton@kealia.com>
To: gdb-patches@sources.redhat.com
Cc: Elena Zannoni <ezannoni@redhat.com>,
Michael Elizabeth Chastain <mec@shout.net>
Subject: Re: [rfa] fix for PR c++/1553
Date: Tue, 24 Feb 2004 20:59:00 -0000 [thread overview]
Message-ID: <yf2ad38ry6q.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20040224200332.GA3747@nevyn.them.org> (Daniel Jacobowitz's message of "Tue, 24 Feb 2004 15:03:32 -0500")
On Tue, 24 Feb 2004 15:03:32 -0500, Daniel Jacobowitz <drow@mvista.com> said:
> I think your handling for nested classes in determine_prefix is
> wrong also; it walks the parents of structs even though structs are
> sometimes given fully qualified names.
Eek! I think you are correct. And that will be extra-fun to come up
with a test case for, given the vagaries of GCC debug output.
I'll add that to my list of things to clean up, then. (But, just to
be clear, I'm leaving the current rfa'd patch as-is: this will be a
subsequent cleanup.)
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2004-02-24 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 18:10 David Carlton
2004-02-24 20:03 ` Daniel Jacobowitz
2004-02-24 20:59 ` David Carlton [this message]
2004-03-19 0:09 ` David Carlton
2004-03-01 17:51 ` 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=yf2ad38ry6q.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=ezannoni@redhat.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