public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: laurent@ient.rwth-aachen.de
To: gcc-gnats@gcc.gnu.org
Subject: c++/8622: typename of base class
Date: Fri, 22 Nov 2002 22:36:00 -0000	[thread overview]
Message-ID: <20021118162824.26903.qmail@sources.redhat.com> (raw)


>Number:         8622
>Category:       c++
>Synopsis:       typename of base class
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Nov 18 08:36:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     laurent@ient.rwth-aachen.de
>Release:        gcc3.2
>Organization:
>Environment:
cygwin, probably every other
>Description:
A type definition, defined by a template typename in a base class, is not understood in the derived class.
This work with Visual 7 or Intel Compiler 6, but gcc gives the following unjustified warnings:

warnings: 'typename B<V>::value_type' is implicitly a typename
warnings: implicit typename is deprecated, please see the documentation for details

Am I wrong ?
If it is really a bug, please correct it, because it is quite important for my big project.

Patrick
>How-To-Repeat:
template<class V>
struct value_traits
{
  typedef V value_type;
};


template<class V>
struct A
{
  typedef typename value_traits<V>::value_type value_type;
};

template<class V>
struct B : public A<V>
{
  value_type v;
};

int main()
{
  B<int> b;
  return 0;
}
>Fix:

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


             reply	other threads:[~2002-11-18 16:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-22 22:36 laurent [this message]
2002-11-23  0:06 gdr
2002-11-23  0:11 Gabriel Dos Reis
2002-11-26  5:56 Gabriel Dos Reis

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=20021118162824.26903.qmail@sources.redhat.com \
    --to=laurent@ient.rwth-aachen.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).