In building a large application, I ran across the following error messages
that do not contain the string 'error:', which makes them harder to fish
out of the log with a regular expression:
"xxx" redefined
#error "xxx"
#warning "xxx"
xxx: No such file or directory
character constant too long for its type
extra tokens at end of #endif directive
extra tokens at end of #include directive
extra tokens at end of #undef directive
invalid suffix "xxx" on floating constant
invalid suffix "xxx" on integer constant
macro "xxx" passed 3 arguments, but takes just 1
multi-line comment
no newline at end of file
pasting "xxx" and "xxx" does not give a valid preprocessing token
trigraph xxx ignored, use -trigraphs to enable
undefined reference to `xxx'
unterminated argument list invoking macro "xxx"
gcc should emit the word 'error:' in front of each
of these error messages to make it easier to grep for
errors. (OK, one of those is an ld error, but I left it in
anyway :-)
--
Summary: add keyword 'error:' to remaining error messages that
lack it
Product: gcc
Version: 3.4.1
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dank at kegel dot com
CC: gcc-bugs at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19027
