This is the mail archive of the
mailing list for the GCC project.
Re: Confusing errormessage with implicit typename
- From: Nicolas Pavlidis <pavnic at sbox dot tugraz dot at>
- To: James E Wilson <wilson at specifixinc dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: 04 Sep 2004 17:41:10 +0200
- Subject: Re: Confusing errormessage with implicit typename
- References: <E1C2newemail@example.com><41390C3B.firstname.lastname@example.org>
James E Wilson <email@example.com> writes:
> Nicolas Pavlidis wrote:
> > /home/pavnic/projects/converter/src/utilities/factory.h:151: warning:
> > implicit typename is deprecated, please see the documentation for
> > details
> The deprecated feature has been removed, and as a result, we can no
> longer give this warning. Since we have no code to support implicit
> typename, it is difficult to impossible to give an error complaining
> about when it occurs.
I know that this was deprecated, but I think if typename is expected at
this point gcc could tell me this, in my example:
error: typename expected but 'iterator' found
> The g++ parser was extensively rewritten between gcc-3.3 and gcc-3.4
> in order to fix some long standing parsing bugs. The result is that
> we have much better C++ conformance, but unfortunately, in some cases,
> the warnings/errors aren't going to be as good as they used to be.
Mayby it is possible to improve the warning/error messages. It is quite
hard to understand some messages that gcc tells.
> We have documented the common problems in the gcc-3.4 release notes. See
> Implicit typename is the third bullet.
| Nicolas Pavlidis | Elvis Presly: |\ |__ |
| Student of SE & KM | "Into the goto" | \|__| |
| firstname.lastname@example.org | ICQ #320057056 | |
|-------------------University of Technology, Graz----------------|