From: Keith Seitz <keiths@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: FAIL: gdb.cp/cpexprs.exp: list base::overload(void)
Date: Fri, 01 Apr 2011 15:53:00 -0000 [thread overview]
Message-ID: <4D95F4FA.9080508@redhat.com> (raw)
In-Reply-To: <201104011609.07889.pedro@codesourcery.com>
On 04/01/2011 08:09 AM, Pedro Alves wrote:
>> # Overloaded methods (all are const -- we try to use the void
>> # method with and without specifying "const")
>
> Why is the non-const variant tried and expected to pass?
Yes, as you say:
> Is this trying to be a reminder that GDB could be more forgiving
> and accept the non-const overload, perhaps?
I wouldn't go so far as to say that gdb needs to be forgiving. This case
is unambiguous, and IMO it is simply a bug/mis-feature. I put those
tests there as a reminder that someone needs to figure out how to fix
this... But:
> Can we just drop it, like below?
Perhaps it would have been better to either XFAIL or remove them
altogether and add a bugzilla entry to track this. I was hoping to get
to it, but as it turned out, there were "bigger fish to fry. :-(
Keith
next prev parent reply other threads:[~2011-04-01 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 15:09 Pedro Alves
2011-04-01 15:53 ` Keith Seitz [this message]
2011-04-01 16:09 ` Pedro Alves
2011-04-01 16:28 ` Pedro Alves
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=4D95F4FA.9080508@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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