This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: c/7356: syntax errors immediately before an #include are reported for within the included file
- From: bangerth at dealii dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, jastrother at hotmail dot com, nobody at gcc dot gnu dot org
- Date: 17 Dec 2002 00:50:52 -0000
- Subject: Re: c/7356: syntax errors immediately before an #include are reported for within the included file
- Reply-to: bangerth at dealii dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, jastrother at hotmail dot com, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
Old Synopsis: misreports error location
New Synopsis: syntax errors immediately before an #include are reported for within the included file
State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Mon Dec 16 16:50:52 2002
State-Changed-Why:
True, still happens with 3.3CVS. Maybe it would be possibly
to identify the position of the token right before the
point where we give the error, i.e. when the output
(as in this example) is
tmp/g> /home/bangerth/bin/gcc-3.3-pre/bin/c++ x.cc
In file included from /usr/include/stdlib.h:33,
from x.cc:2:
/home/bangerth/bin/gcc-3.3-pre/lib/gcc-lib/i686-pc-linux-gnu/3.3/include/stddef.h:213: error: syntax
error before `typedef'
then also output the position of the token before the
"typedef" token, at least if it is in another file.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7356