public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/5094: partial specialisation cannot be friend?? Date: Wed, 12 Dec 2001 20:06:00 -0000 [thread overview] Message-ID: <20011213040603.2783.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/5094; it has been noted by GNATS. From: rodrigc@gcc.gnu.org To: benko@sztaki.hu, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c++/5094: partial specialisation cannot be friend?? Date: 13 Dec 2001 03:58:51 -0000 Synopsis: partial specialisation cannot be friend?? State-Changed-From-To: open->analyzed State-Changed-By: rodrigc State-Changed-When: Wed Dec 12 19:58:51 2001 State-Changed-Why: This is not a bug in gcc. This is not legal code. When I compile with the Digital Unix C++ compiler, I get the following compilation errors: cxx: Error: specfriend.cc, line 67: "c" has already been declared in the current scope friend class c; -----------------^ cxx: Error: specfriend.cc, line 71: class "c" may not have a template argument list friend class d<c<T> >; -----------------^ cxx: Error: specfriend.cc, line 71: class "c" may not have a template argument list friend class d<c<T> >; -----------------^ cxx: Error: specfriend.cc, line 71: invalid partial specialization -- class "d<<error-type>>" is already fully specialized friend class d<c<T> >; ---------------^ cxx: Error: specfriend.cc, line 83: class "c" may not have a template argument list friend class c<d>; ---------------^ cxx: Info: 5 errors detected in the compilation of "specfriend.cc". http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5094&database=gcc
next reply other threads:[~2001-12-13 4:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-12-12 20:06 rodrigc [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-19 7:36 lerdsuwa 2001-12-14 0:16 Pal Benko 2001-12-12 20:16 Martin Sebor 2001-12-12 19:58 rodrigc 2001-12-12 7:26 benko
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=20011213040603.2783.qmail@sources.redhat.com \ --to=rodrigc@gcc.gnu.org \ --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).