public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gccbugs at contacts dot eelis dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/11786] New: operator() call on variable in other namespace not recognized Date: Mon, 04 Aug 2003 06:32:00 -0000 [thread overview] Message-ID: <20030804063201.11786.gccbugs@contacts.eelis.net> (raw) PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11786 Summary: operator() call on variable in other namespace not recognized Product: gcc Version: 3.4 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: gccbugs at contacts dot eelis dot net CC: gcc-bugs at gcc dot gnu dot org GCC rejects the following valid code: struct S { template <typename T> void operator() (T) {} }; namespace N { S s; struct A {} a; } using N::s; void f () { s(N::a); } GCC says: t.cpp:8: error: `N::s' is not a function, t.cpp:8: error: conflict with `N::s' t.cpp:14: error: in call to `s' My best guess would be that GCC does not recognize s(..) as a call to operator() on _variable_ N::s, and as such insists on finding a _function_ named 'N::s'. I haven't got a clue as to what the rest of the error message indicates or how A is involved. Comeau compiles the code without problems. I'm using GCC 3.4 20030723.
next reply other threads:[~2003-08-04 6:32 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-08-04 6:32 gccbugs at contacts dot eelis dot net [this message] 2003-08-04 7:28 ` [Bug c++/11786] " gccbugs at contacts dot eelis dot net 2003-08-04 19:46 ` pinskia at physics dot uc dot edu 2003-08-04 23:02 ` [Bug c++/11786] [3.3/3.4 regression] " reichelt at gcc dot gnu dot org 2003-09-08 18:46 ` cvs-commit at gcc dot gnu dot org 2003-09-08 19:05 ` cvs-commit at gcc dot gnu dot org 2003-09-08 19:15 ` mmitchel at gcc dot gnu dot 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=20030804063201.11786.gccbugs@contacts.eelis.net \ --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: linkBe 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).