public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55576] Fails to compile a call to template member function
Date: Thu, 06 Dec 2012 16:33:00 -0000 [thread overview]
Message-ID: <bug-55576-4-jpqIjf1B9s@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55576-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55576
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |NEW
Last reconfirmed| |2012-12-06
Resolution|INVALID |
Ever Confirmed|0 |1
--- Comment #9 from Jason Merrill <jason at gcc dot gnu.org> 2012-12-06 16:33:09 UTC ---
3.4.5 seems clear on this point:
The identifier is first looked up in the class of the object expression. If the
identifier is not found, it is then looked up in the context of the entire
postfix-expression and shall name a class template.
So the testcase in comment 3 is valid.
next prev parent reply other threads:[~2012-12-06 16:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 15:27 [Bug c++/55576] New: " antoshkka at gmail dot com
2012-12-03 16:01 ` [Bug c++/55576] " redi at gcc dot gnu.org
2012-12-03 16:08 ` paolo.carlini at oracle dot com
2012-12-04 7:13 ` antoshkka at gmail dot com
2012-12-04 9:38 ` paolo.carlini at oracle dot com
2012-12-04 10:48 ` glisse at gcc dot gnu.org
2012-12-04 11:05 ` redi at gcc dot gnu.org
2012-12-06 14:39 ` antoshkka at gmail dot com
2012-12-06 15:47 ` redi at gcc dot gnu.org
2012-12-06 16:33 ` jason at gcc dot gnu.org [this message]
2012-12-13 18:02 ` tudorb at fb dot com
2012-12-13 18:04 ` tudorb at fb dot com
2013-02-25 14:07 ` potswa at mac dot com
2013-02-25 16:20 ` d.frey at gmx dot de
2013-03-16 9:45 ` paolo.carlini at oracle dot com
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=bug-55576-4-jpqIjf1B9s@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).