public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: wolfgang.bangerth@iwr.uni-heidelberg.de
To: gcc-gnats@gcc.gnu.org
Subject: c++/7348: More recent access control problems, and wrong implicit typename warnings
Date: Thu, 18 Jul 2002 01:46:00 -0000	[thread overview]
Message-ID: <20020718083815.22230.qmail@sources.redhat.com> (raw)


>Number:         7348
>Category:       c++
>Synopsis:       More recent access control problems, and wrong implicit typename warnings
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jul 18 01:46:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Wolfgang Bangerth
>Release:        unknown-1.0
>Organization:
>Environment:
gcc 3.2 pre 2002-07-17
>Description:
The following fails to compile:
---------------------------------------------
class Outer {
    template <int dim> struct Inner {
	typedef int T;
	T foo ();
    };
  public:
    Outer();
};

template <int dim>
typename Outer::Inner<dim>::T  Outer::Inner<dim>::foo () {
  return 1;
};

template Outer::Inner<2>;
--------------------------------------------

The messages are:
x.cc:2: error: `template<int dim> struct Outer::Inner' is private
x.cc:11: error: within this context
x.cc:11: warning: `Outer::Inner<dim>::T' is implicitly a
          typename
x.cc:11: warning: implicit typename is deprecated, please 
          see the documentation for details

Since Outer::Inner<dim>::T is the only way to access the 
return type of the function, this must be allowed. 
Furthermore, the implicit typename warning is bogus, since 
there a "typename" on this very line.

This, just as c++/7347 is a new failure. Again, the bug
goes away if the inner class is not a template, which is 
suspicious at best :-)

Regards
  Wolfgang
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-07-18  8:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18  1:46 wolfgang.bangerth [this message]
2002-07-18  6:26 lerdsuwa
2002-07-18  8:39 lerdsuwa
2002-07-23  7:25 lerdsuwa

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=20020718083815.22230.qmail@sources.redhat.com \
    --to=wolfgang.bangerth@iwr.uni-heidelberg.de \
    --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).