* C++ cpp lineno breakage
@ 2004-10-12 22:59 Mike Stump
2004-10-13 1:05 ` Zack Weinberg
0 siblings, 1 reply; 2+ messages in thread
From: Mike Stump @ 2004-10-12 22:59 UTC (permalink / raw)
To: GCC Mailing List
Hey, Matt, Zack, did you break:
char *p = "\q"; /* { dg-error "unknown escape" } */
int i;
this recently for C++? The problem is the line numbers for cpp_error
come out as the last line number in the source file. In the above, we
currently see:
t.cc:2:1: warning: unknown escape sequence '\q'
instead of:
t.cc:1:11: warning: unknown escape sequence '\q'
(which is what we see in C).
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: C++ cpp lineno breakage
2004-10-12 22:59 C++ cpp lineno breakage Mike Stump
@ 2004-10-13 1:05 ` Zack Weinberg
0 siblings, 0 replies; 2+ messages in thread
From: Zack Weinberg @ 2004-10-13 1:05 UTC (permalink / raw)
To: Mike Stump; +Cc: GCC Mailing List
Mike Stump <mrs@apple.com> writes:
> Hey, Matt, Zack, did you break:
>
> char *p = "\q"; /* { dg-error "unknown escape" } */
> int i;
>
> this recently for C++? The problem is the line numbers for cpp_error
> come out as the last line number in the source file.
That seems like a plausible problem falling out of the
lex-everything-first patch. Please file a bug report and assign it to
me.
zw
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-10-12 23:00 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-10-12 22:59 C++ cpp lineno breakage Mike Stump
2004-10-13 1:05 ` Zack Weinberg
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).