public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/24702] Koenig found functoid ref, but "cannot be used as a function"
Date: Mon, 07 Nov 2005 13:37:00 -0000 [thread overview]
Message-ID: <20051107133658.29631.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24702-11665@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from pinskia at gcc dot gnu dot org 2005-11-07 13:36 -------
Actually IIRC Koenig lookup only finds functions and not variables. If that is
the case we have two issues here. One is we accept invalid and another is that
error message is wrong.
Note ICC rejects this:
t.cc(26): error: identifier "dummyFunct" is undefined
std::cout<<"dummyFunct(d) = "<<dummyFunct(d)<<std::endl; // fails with 3.4
^
t.cc(28): error: identifier "myDummyFunct" is undefined
std::cout<<"myDummyFunct(d) = "<<myDummyFunct(d)<<std::endl;
^
t.cc(29): error: identifier "mymyDummyFunct" is undefined
std::cout<<"mymyDummyFunct(d) = "<<mymyDummyFunct(d)<<std::endl; // fails
^
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24702
next prev parent reply other threads:[~2005-11-07 13:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 7:09 [Bug c++/24702] New: " pierhyth at gmail dot com
2005-11-07 13:37 ` pinskia at gcc dot gnu dot org [this message]
2005-11-09 1:33 ` [Bug c++/24702] " pierhyth at gmail dot com
2005-11-16 19:28 ` gdr at integrable-solutions dot net
2005-12-04 5:09 ` gdr at gcc dot gnu dot org
[not found] <bug-24702-4@http.gcc.gnu.org/bugzilla/>
2013-09-05 14:29 ` paolo.carlini at oracle dot com
2013-09-05 14:40 ` redi at gcc dot gnu.org
2013-09-05 14:43 ` redi at gcc dot gnu.org
2013-09-05 15:18 ` paolo.carlini at oracle dot com
2013-09-06 1:19 ` pierhyth at gmail dot com
2013-09-06 7:30 ` redi at gcc dot gnu.org
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=20051107133658.29631.qmail@sourceware.org \
--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).