Re: Degraded C++ error messages

[Wolfgang Bangerth <bangerth at ices dot utexas dot edu>]

> Being mainly
> a *user* of g++, it is my experience that the error messages
> have gotten less and less practical value.

That's right, and we have a number of open reports about this:
http://gcc.gnu.org/bugzilla/buglist.cgi?query_format=&short_desc_type=allwordssubstr&short_desc=&component=c%2B%2B&target_milestone=3.3.3&target_milestone=3.4&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&gcchost_type=allwordssubstr&gcchost=&gcctarget_type=allwordssubstr&gcctarget=&gccbuild_type=allwordssubstr&gccbuild=&keywords_type=allwords&keywords=diagnostic&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&notchangedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&field0-0-0=noop&type0-0-0=noop&value0-0-0=
 
The new parser has introduced most of these regressions, and unfortunately I 
don't see much activity in changing the present state. I hope that a 
significant number of these things will be fixed by the time 3.4 goes out the 
door.

In the meantime, feel free to report these things to bugzilla!

W.

-------------------------------------------------------------------------
Wolfgang Bangerth              email:            bangerth@ices.utexas.edu
                               www: http://www.ices.utexas.edu/~bangerth/