public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: dv@vollmann.ch, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: c++/8389: [mainline regression] Access to members of base class & templates
Date: Tue, 29 Oct 2002 07:39:00 -0000	[thread overview]
Message-ID: <20021029153916.23874.qmail@sources.redhat.com> (raw)

Old Synopsis: Cannot access protected member in base class
New Synopsis: [mainline regression] Access to members of base class & templates

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Tue Oct 29 07:39:14 2002
State-Changed-Why:
    Confirmed. It works in 3.2.1pre, though. The shortest example
    I can come up with is this:
    ----------------------------------
    template <class>
    class Base {
      protected:
        typedef int Type;
    };
    
    template <class T>
    struct Derived : public Base<T> {
        typedef typename Base<T>::Type Type;
    
        template <class Arg>
        void f(Type = Type()) {};
    };
    
    template void Derived<char>::f<int> (Type);
    -----------------------------------
    Making one of the templates a non-template makes the bug
    go away. What is also surprising is the three-fold output
    gcc gives:
    --------------------------------------
    tmp/g> /home/bangerth/bin/gcc-3.3-pre/bin/c++ -ansi -pedantic -W -Wall -c x.cc
    x.cc:4: error: `typedef int Base<char>::Type' is protected
    x.cc:12: error: within this context
    x.cc:4: error: `typedef int Base<char>::Type' is protected
    x.cc:12: error: within this context
    x.cc:4: error: `typedef int Base<char>::Type' is protected
    x.cc:15: error: within this context
    --------------------------------------

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8389


             reply	other threads:[~2002-10-29 15:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-29  7:39 bangerth [this message]
2002-11-01  6:28 lerdsuwa
2002-11-10  1:08 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=20021029153916.23874.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=dv@vollmann.ch \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@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: 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).