This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/22573] typedef in class scope not reported by error message
- From: "gdr at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 30 Nov 2005 17:43:57 -0000
- Subject: [Bug c++/22573] typedef in class scope not reported by error message
- References: <bug-22573-2045@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from gdr at gcc dot gnu dot org 2005-11-30 17:43 -------
(In reply to comment #2)
> Absolutely not! There is no "best" way: sometimes it is better to go through
> the typedef, sometimes it is better to print the typedef.
>
> To tell you the truth, I consider the fact that GCC prints both a *feature*.
>
> However, we should decide whether the inconsistency is a bug. Gaby?
I don't think there is "the best" way to deal with this.
One can think of moving to diagnostic with carrets so that we print
what user wrote; but that does not solve the core issue (see exiting
compilers that hve diagnostic-with-carrets), especially when getting
messages from instantiation contexts.
I don't consider it a bug.
--
gdr at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22573