From: David Carlton <carlton@kealia.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/c++] cp_lookup_rtti_type, take 2
Date: Fri, 05 Dec 2003 16:57:00 -0000 [thread overview]
Message-ID: <yf265gvp5gr.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20031205032959.GA13165@nevyn.them.org> (Daniel Jacobowitz's message of "Thu, 4 Dec 2003 22:29:59 -0500")
On Thu, 4 Dec 2003 22:29:59 -0500, Daniel Jacobowitz <drow@mvista.com> said:
> On Mon, Dec 01, 2003 at 04:40:39PM -0500, Michael Chastain wrote:
>> . The calls to lookup_rtti_type need a proper "block" parameter.
>> The old code needed this too; I haven't regressed anything.
>> I put FIXME notes in for this.
> I'm not as sure as you are about this - certainly we do _not_ want a
> block that came down the call chain; think about what dynamic type
> is.
Good point. Oops.
> Ignoring anonymous namespaces for now.)
Yes...
> Now that we've had another major release of GDB I am extremely
> tempted to rip out aCC C++ support.
You'll get no complaints from me.
>> . Nested types give a warning and don't work.
>> It would be nice to make them work.
> It's a pain. I spent quite some time trying to sort out the issues.
> I'll give it a shot again after more of David's patches have been
> merged.
I think they should work okay after my patch that is waiting for
approval gets applied?
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2003-12-05 16:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 21:40 Michael Elizabeth Chastain
2003-12-05 3:30 ` Daniel Jacobowitz
2003-12-05 16:57 ` David Carlton [this message]
2003-12-05 17:16 ` Daniel Jacobowitz
2003-12-05 4:23 Michael Elizabeth Chastain
2003-12-05 5:01 ` Daniel Jacobowitz
2003-12-05 17:12 ` David Carlton
2003-12-05 17:16 ` Daniel Jacobowitz
2003-12-05 17:38 ` David Carlton
2003-12-05 17:40 ` Daniel Jacobowitz
2003-12-05 5:26 Michael Elizabeth Chastain
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=yf265gvp5gr.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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