From: Nicolas Pavlidis <pavnic@sbox.tugraz.at>
To: James E Wilson <wilson@specifixinc.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Confusing errormessage with implicit typename
Date: Sat, 04 Sep 2004 15:41:00 -0000 [thread overview]
Message-ID: <m3zn46nisp.fsf@malloc.pavnic> (raw)
In-Reply-To: <41390C3B.6040203@specifixinc.com>
James E Wilson <wilson@specifixinc.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
> http://gcc.gnu.org/gcc-3.4/changes.html#cplusplus
> Implicit typename is the third bullet.
Thx!
Best regards,
Nicolas
--
| Nicolas Pavlidis | Elvis Presly: |\ |__ |
| Student of SE & KM | "Into the goto" | \|__| |
| pavnic@sbox.tugraz.at | ICQ #320057056 | |
|-------------------University of Technology, Graz----------------|
next prev parent reply other threads:[~2004-09-04 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1C2new-0007o7-00@deer.gmane.org>
2004-09-04 0:28 ` James E Wilson
2004-09-04 0:38 ` Joe Buck
2004-09-04 15:41 ` Nicolas Pavlidis [this message]
2004-09-04 15:48 ` Robert Dewar
2004-09-02 9:13 Nicolas Pavlidis
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=m3zn46nisp.fsf@malloc.pavnic \
--to=pavnic@sbox.tugraz.at \
--cc=gcc@gcc.gnu.org \
--cc=wilson@specifixinc.com \
/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).