Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@kealia.com>
Cc: gdb-patches@sources.redhat.com,
	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:03:00 -0000	[thread overview]
Message-ID: <20040224200332.GA3747@nevyn.them.org> (raw)
In-Reply-To: <m3ptc4nyb9.fsf@coconut.kealia.com>

On Tue, Feb 24, 2004 at 10:10:18AM -0800, David Carlton wrote:
> Here's a fix for PR c++/1553.  It cleans up a botch I made in
> dwarf2read.c:read_structure_scope: I had all this conditional logic
> for determining the name, including a case where the code basically
> says "well, it would be a little bit of work to get the name right
> now, so let's remember that we got it wrong and try to fix the
> situation later".  And, of course, not only is this fragile and a
> maintenance problem, it proved to be buggy - I got abstract
> declarations of nested classes wrong, basically.

FWIW, the new logic looks right to me, and the old logic was definitely
wrong; I noticed it when I tried to separate this function in two on
the intercu branch on Sunday.

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.  I think I managed to create a testcase
where class names would be repeated.  But now I can't find the testcase
so I may have been playing with my own broken code instead.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-02-24 20:03 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 [this message]
2004-02-24 20:59   ` David Carlton
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=20040224200332.GA3747@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=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