From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: RFC: fix PR c++/8888
Date: Thu, 22 Nov 2012 02:20:00 -0000 [thread overview]
Message-ID: <871ufml6o6.fsf@fleche.redhat.com> (raw)
In-Reply-To: <87boeqlk45.fsf@fleche.redhat.com> (Tom Tromey's message of "Wed, 21 Nov 2012 14:30:18 -0700")
>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
Tom> After investigating the problem for a while, I couldn't find a bad
Tom> situation here other than the constructor problem. So, I made the fix
Tom> specific to this case.
... and of course, thought of one later: the name of a superclass
constructor will also cause the same failure. I'll look at this next
week.
Tom
prev parent reply other threads:[~2012-11-22 2:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 21:30 Tom Tromey
2012-11-22 2:20 ` Tom Tromey [this message]
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=871ufml6o6.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
/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