public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c/3487: unrecognized token before #include points to wrong source
@ 2002-02-23 18:41 rodrigc
0 siblings, 0 replies; 2+ messages in thread
From: rodrigc @ 2002-02-23 18:41 UTC (permalink / raw)
To: 85908-quiet, gcc-bugs, gcc-prs, jb, nobody
Synopsis: unrecognized token before #include points to wrong source
State-Changed-From-To: analyzed->closed
State-Changed-By: rodrigc
State-Changed-When: Sat Feb 23 18:36:30 2002
State-Changed-Why:
Not a bug.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3487
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: c/3487: unrecognized token before #include points to wrong source
@ 2001-07-02 4:07 neil
0 siblings, 0 replies; 2+ messages in thread
From: neil @ 2001-07-02 4:07 UTC (permalink / raw)
To: 85908-quiet, gcc-bugs, gcc-prs, jb, nobody
Synopsis: unrecognized token before #include points to wrong source
State-Changed-From-To: open->analyzed
State-Changed-By: neil
State-Changed-When: Mon Jul 2 04:07:24 2001
State-Changed-Why:
I'm far from convinced this is a bug, or even undesirable behaviour - the compiler reports its position when it finds a syntax error. In some weird cases, this happens to be in the header file.
In any case, the cause is the front end and not the preprocessor. I'll let a C front end maintainer decide.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3487&database=gcc
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-02-24 2:36 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-02-23 18:41 c/3487: unrecognized token before #include points to wrong source rodrigc
-- strict thread matches above, loose matches on Subject: below --
2001-07-02 4:07 neil
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).