From: "erwan ancel" <erwan.ancel@free.fr>
To: <gcc-help@gcc.gnu.org>
Subject: Re: implicit typename is deprecated
Date: Mon, 27 Jan 2003 17:11:00 -0000 [thread overview]
Message-ID: <012d01c2c627$15d0e0f0$0100a8c0@brisedorient> (raw)
In-Reply-To: <x3lm16dggo.fsf@lifesupport.shutdown.com>
thanks a lot. I got my answer :)
----- Original Message -----
From: "LLeweLLyn Reese" <llewelly@lifesupport.shutdown.com>
To: "erwan ancel" <erwan.ancel@free.fr>
Cc: <gcc-help@gcc.gnu.org>
Sent: Monday, January 27, 2003 11:39 AM
Subject: Re: implicit typename is deprecated
> "erwan ancel" <erwan.ancel@free.fr> writes:
>
> > Hi,
> > Does anyone know what this mean ?
> > "Implicit typename is deprecated"
>
> Dependent names which are type names are required to be qualified by
> the keyword 'typename'.
>
> A dependent name is a name which is dependent on a template parameter.
>
> struct A
> {
> struct nest{};
> };
>
> template<class T>
> struct contain
> {
> typedef typename T::nest;
> };
>
> In the example above, 'T::nest' is a dependent name. Other common
> dependent names are things like 'vector<T>::value_type' . Since
> the parameters with which a template will be instantiated cannot
> be known in general, and a given type may delcare 'nest' as a
> static member, a data member, or a type member, or not at all, it
> was felt the user should indicate when a dependent name is
> intended/expected to be a type name. This allows better error
> reporting, and potentially simpler implementation.
>
> > I got this message when compiling my template instanciations with gcc
3.2,
> > and the compilation fails, but I managed to compile this without any
> > warning/error with gcc 2.95.
> [snip]
>
> 3.2 is much closer to conformance than 2.95
>
prev parent reply other threads:[~2003-01-27 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-26 11:29 erwan ancel
2003-01-26 12:19 ` erwan ancel
2003-01-27 10:42 ` LLeweLLyn Reese
2003-01-27 17:11 ` erwan ancel [this message]
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='012d01c2c627$15d0e0f0$0100a8c0@brisedorient' \
--to=erwan.ancel@free.fr \
--cc=gcc-help@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).