public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Martin Sebor <sebor@roguewave.com>
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:16:00 -0000	[thread overview]
Message-ID: <20011213041601.9453.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]

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

From: Martin Sebor <sebor@roguewave.com>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/5094: partial specialisation cannot be friend??
Date: Wed, 12 Dec 2001 21:23:58 -0700

 rodrigc@gcc.gnu.org wrote:
 > 
 > 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:
 
 Although I also have respect for the latest version of Compaq C++,
 it should be noted that the compiler isn't "the ultimate authority"
 on the validity of C++ code. What clenches it is that 14.5.3, p9
 explicitly prohibits friend declarations of partial specializations:
 
   -9- Friend declarations shall not declare partial specializations.
       [Example:
           template<class T> class A { };
           class X {
               template<class T> friend class A<T*>; // error
           };
       —end example]
 
 Regards
 Martin


             reply	other threads:[~2001-12-13  4:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-12 20:16 Martin Sebor [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:06 rodrigc
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=20011213041601.9453.qmail@sources.redhat.com \
    --to=sebor@roguewave.com \
    --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).