public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: lerdsuwa@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, ndry@mdcplus.com,
	nobody@gcc.gnu.org
Subject: Re: c++/7218: incorrect 'implicit typename' warnings
Date: Thu, 11 Jul 2002 07:50:00 -0000	[thread overview]
Message-ID: <20020711145001.10318.qmail@sources.redhat.com> (raw)

Synopsis: incorrect 'implicit typename' warnings

State-Changed-From-To: open->closed
State-Changed-By: lerdsuwa
State-Changed-When: Thu Jul 11 07:50:00 2002
State-Changed-Why:
    Not a bug.  AA is inside template-parameter dependent
    base class.  When parsing class B, names inside A<T>
    are not looked up.  You have to write
      template<class T>
      struct B : A<T> { typename A<T>::AA a;};

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


             reply	other threads:[~2002-07-11 14:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-11  7:50 lerdsuwa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-13  3:26 Kriang Lerdsuwanakij
2002-07-12 12:56 Ryohei Noda
2002-07-05 19:16 ndry

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=20020711145001.10318.qmail@sources.redhat.com \
    --to=lerdsuwa@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=ndry@mdcplus.com \
    --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).