This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/65448] New: Allow for cascade includes in error messages
- From: "ethouris at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 17 Mar 2015 09:26:04 +0000
- Subject: [Bug c++/65448] New: Allow for cascade includes in error messages
- Auto-submitted: auto-generated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65448
Bug ID: 65448
Summary: Allow for cascade includes in error messages
Product: gcc
Version: 4.9.1
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ethouris at gmail dot com
When gcc reports a compile error that refers to a line in a file that is
included by another include file, which is finally included by the *.cpp file
being compiled, it reports the error more-less this way:
In file included from file1.h:10:1,
from file2.h:11:1,
from file.cpp:9:0:
file3.h:25:0: error: 'symbol' does not name a type
Most tools that use these error reports simply skip the first three lines, as
they do not look like "standard compiler error format". It would be nice to
have at least an option to change the format into something like this:
file1.h:10:1: note: In file included from here,
file2.h:11:1: note: from here,
file.cpp:9:0: note: from here,
file3.h:25:0: error: 'symbol' does not name a type
Some programming mistakes are very tough to determine without the cascade
include information (such as forgetting a semicolon in some declaration before
an #include directive).