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:16:00 -0000 [thread overview] Message-ID: <20030108191606.19824.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: reichelt@igpm.rwth-aachen.de Cc: bangerth@ticam.utexas.edu, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/9230: Friend definitions in template classes Date: 08 Jan 2003 20:07:15 +0100 reichelt@igpm.rwth-aachen.de writes: | Synopsis: Friend definitions in template classes | | State-Changed-From-To: open->feedback | State-Changed-By: reichelt | State-Changed-When: Wed Jan 8 09:14:33 2003 | State-Changed-Why: | As I read paragraph 14.6.5.1 in the standard, this is the expected behavior: | | > Friend classes or functions can be declared within a class template. When | > a template is instantiated, the names of its friends are treated as if | > the specialization had been explicitly declared at its point of instantiation. Declared *where*? | Convinced, Wolfgang? I'm not Wolfgang but I'm not convinced. Read on 14.6.5/2: As with non-template classes, the names of namespace-scope friend functions of a class template special-ization are not visible during an ordinary lookup unless explicitly declared at namespace scope (11.4). Such names may be found under the rules for associated classes (3.4.2). -- Gaby
next reply other threads:[~2003-01-08 19:16 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-08 19:16 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:06 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=20030108191606.19824.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: 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).