public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9230: Friend definitions in template classes
Date: Wed, 08 Jan 2003 19:06:00 -0000	[thread overview]
Message-ID: <20030108190609.12427.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/9230; it has been noted by GNATS.

From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: bangerth@ticam.utexas.edu
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/9230: Friend definitions in template classes
Date: 08 Jan 2003 20:01:57 +0100

 bangerth@ticam.utexas.edu writes:
 
 | I'm not sure about this one:
 | --------------------------
 | template <class T> class X {
 |     friend void f () {};
 | };
 | 
 | void g() { f(); }
 | --------------------------
 | This yields:
 | h.cc: In function `void g()':
 | h.cc:5: error: `f' undeclared (first use this function)
 | h.cc:5: error: (Each undeclared identifier is reported only once for each
 |    function it appears in.)
 | 
 | On the other hand, this compiles cleanly:
 | --------------------------
 | template <class T> class X {
 |     friend void f () {};
 | };
 | 
 | template class X<int>;
 | void g() { f(); }
 
 This  is a bogus behaviour of g++ I came across from time to time.
 More generally, we have BIG problems in the current name-lookup
 implementation.
 
 | In other words, the function f() is injected into the global
 | namespace only upon the first instantiation of the template
 | class X. Is this the way it is supposed to be?
 
 No.
 
 There is no declaration of f() in the global scope.
 
 -- Gaby


             reply	other threads:[~2003-01-08 19:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 19:06 Gabriel Dos Reis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-29 20:03 bangerth
2003-01-08 19:37 bangerth
2003-01-08 19:16 Gabriel Dos Reis
2003-01-08 19:16 Gabriel Dos Reis
2003-01-08 17:26 Wolfgang Bangerth
2003-01-08 17:25 reichelt
2003-01-08 17:14 reichelt
2003-01-08 16:46 bangerth

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=20030108190609.12427.qmail@sources.redhat.com \
    --to=gdr@integrable-solutions.net \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).