public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/17045] conflict between function template and class with same name
Date: Mon, 16 Aug 2004 14:53:00 -0000	[thread overview]
Message-ID: <20040816145314.31827.qmail@sourceware.org> (raw)
In-Reply-To: <20040816030839.17045.gccbugs@contacts.eelis.net>


------- Additional Comments From bangerth at dealii dot org  2004-08-16 14:53 -------
What is really happening is that in the instantiation of ::f<N::f>, the 
compiler sees the call 
  f(T()); 
Since the argument T() is of type N::f, it has to look up the name 
of the function in both the global namespace and the namespace of 
the argument, i.e. N (Koenig lookup). It just happens to find the 
latter rather than the former. 
 
An example that may be a little less confusing about reusing names is this: 
--------------------- 
void h (...); 
 
template <typename T> void g () { T t;  h(t); } 
 
namespace N 
{ 
  struct S {}; 
  struct h; 
} 
 
void foo () { g<N::S>(); } 
----------------------- 
g/x> /home/bangerth/bin/gcc-3.5-pre/bin/c++ -c x.cc 
x.cc: In function `void g() [with T = N::S]': 
x.cc:11:   instantiated from here 
x.cc:8: error: `struct N::h' is not a function, 
x.cc:1: error:   conflict with `void h(...)' 
x.cc:3: error:   in call to `h' 
 
W. 

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17045


  parent reply	other threads:[~2004-08-16 14:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-16  3:08 [Bug c++/17045] New: " gccbugs at contacts dot eelis dot net
2004-08-16  3:40 ` [Bug c++/17045] " pinskia at gcc dot gnu dot org
2004-08-16  4:12 ` gccbugs at contacts dot eelis dot net
2004-08-16 14:53 ` bangerth at dealii dot org [this message]
2004-12-21 13:15 ` redi at gcc dot gnu dot org
     [not found] <bug-17045-5473@http.gcc.gnu.org/bugzilla/>
2006-09-19  4:15 ` pinskia 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=20040816145314.31827.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).