public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Matthias Klose <doko@net.local>
To: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org
Subject: c++/10887: [3.3/3.4 regression] specialization of private members structs fails
Date: Tue, 20 May 2003 21:36:00 -0000	[thread overview]
Message-ID: <E19IEgE-0003Yh-1S@tango.net.local> (raw)


>Number:         10887
>Category:       c++
>Synopsis:       [3.3/3.4 regression] specialization of private members structs fails
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Tue May 20 21:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Herbert Valerio Riedel <hvr@se-linux.ifs.tuwien.ac.at>
>Release:        3.3 (Debian) (Debian testing/unstable)
>Organization:
The Debian Project
>Environment:
>Description:
 [ Reported to the Debian BTS as report #193830.
   Please CC 193830@bugs.debian.org on replies.
   Log of report can be found at http://bugs.debian.org/193830 ]
	

3.3 and 3.4 CVS 20030501 fail to compile the following code (which
would compile with previous g++ versions):

$ cat in_class_class.cc
class Foo {
  template <class T> struct InFoo;
};

template<>
struct Foo::InFoo<int> {
    // ...
};
$ g++ -c in_class_class.cc
in_class_class.cc:2: error: `template<class T> struct Foo::InFoo' is private
in_class_class.cc:6: error: within this context
$

>How-To-Repeat:
	
>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-05-20 21:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20 21:36 Matthias Klose [this message]
2003-05-20 21: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=E19IEgE-0003Yh-1S@tango.net.local \
    --to=doko@net.local \
    --cc=193830@bugs.debian.org \
    --cc=debian-gcc@lists.debian.org \
    --cc=gcc-gnats@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).