From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: RFC: fix PR c++/15116
Date: Thu, 21 Feb 2013 19:34:00 -0000 [thread overview]
Message-ID: <87liahbgvu.fsf@fleche.redhat.com> (raw)
In-Reply-To: <87ppztbh2x.fsf@fleche.redhat.com> (Tom Tromey's message of "Thu, 21 Feb 2013 12:30:14 -0700")
>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
Tom> Second, overload resolution can actually do a kind of second overload
Tom> resolution, according to the standard. This is well-formed:
Tom> int f(int x) { return x; }
Tom> double f(double x) { return x; }
A minor note. It turns out that the example as written actually does
work. This is because the correct "f" appears first in the CU.
If you swap these two lines, you can make it fail:
(gdb) p overload(0,f)
Cannot resolve function overload to any overloaded instance
I've pointed this out in the PR I'm filing.
Tom
next prev parent reply other threads:[~2013-02-21 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 19:30 Tom Tromey
2013-02-21 19:34 ` Tom Tromey [this message]
2013-03-15 17:32 ` Tom Tromey
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=87liahbgvu.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