public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "giovannibajo at libero dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/13935] [3.4/3.5 Regression] Template friend lookup bug
Date: Mon, 02 Feb 2004 02:16:00 -0000	[thread overview]
Message-ID: <20040202021644.5294.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040130165003.13935.giovannibajo@libero.it>


------- Additional Comments From giovannibajo at libero dot it  2004-02-02 02:16 -------
(In reply to comment #5)

> That is the same thing as for
>    struct foo { };
>    struct bar {
>       foo foo;
>    };  

I disagree. [class.friend]/1: "The name of a friend is not in the scope of the 
class."

> See 3.3.6/1
>    [...]
>    2) A name N used in a class S shall refer to the same declaration
>       in its context and when reevaluated in the completed scope of
>       S. No diagnostic is required for a violation of this rule.

3.3.6 is [basic.class.scope] and 3.3.6/1 begins with: "The following rules 
describe the scope of names declared in classes". Given [class.friend]/1, I 
don't see how this could apply.


-- 


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


  parent reply	other threads:[~2004-02-02  2:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-30 16:50 [Bug c++/13935] New: " giovannibajo at libero dot it
2004-01-30 16:50 ` [Bug c++/13935] " giovannibajo at libero dot it
2004-01-30 17:10 ` bangerth at dealii dot org
2004-01-30 17:45 ` gdr at integrable-solutions dot net
2004-01-30 17:58 ` giovannibajo at libero dot it
2004-01-30 19:23 ` gdr at integrable-solutions dot net
2004-02-02  2:16 ` giovannibajo at libero dot it [this message]
2004-02-02  2:27 ` gdr at integrable-solutions dot net
2004-02-02  2:35 ` giovannibajo at libero dot it
2004-02-03  9:22 ` 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=20040202021644.5294.qmail@sources.redhat.com \
    --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).