public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51757] friend defined inside class and declared inside main linker error Date: Thu, 05 Jan 2012 10:36:00 -0000 [thread overview] Message-ID: <bug-51757-4-eVlXBifsX9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51757-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51757 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Last reconfirmed| |2012-01-05 Resolution|INVALID | Ever Confirmed|0 |1 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-01-05 10:35:56 UTC --- There is no A::func, that's a friend not a member function. [class.friend] -6- A function can be defined in a friend declaration of a class if and only if the class is a non-local class (9.8), the function name is unqualified, and the function has namespace scope. [ Example: class M { friend void f() { } // definition of global f, a friend of M, // not the definition of a member function }; —end example ] -7- Such a function is implicitly inline. A friend function defined in a class is in the (lexical) scope of the class in which it is defined. A friend function defined outside the class is not (3.4.1).
next prev parent reply other threads:[~2012-01-05 10:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-04 22:38 [Bug c++/51757] New: " neotheone222 at gmail dot com 2012-01-05 1:34 ` [Bug c++/51757] " redi at gcc dot gnu.org 2012-01-05 9:39 ` rguenth at gcc dot gnu.org 2012-01-05 10:36 ` redi at gcc dot gnu.org [this message] 2012-01-05 10:43 ` redi at gcc dot gnu.org 2021-01-18 19:23 ` language.lawyer at gmail dot com 2024-04-06 3:45 ` pinskia 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=bug-51757-4-eVlXBifsX9@http.gcc.gnu.org/bugzilla/ \ --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).