This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c++/22573] typedef in class scope not reported by error message

------- 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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]