This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] GCC caret diagnostics
Ian Lance Taylor <iant@google.com> writes:
>Another approach would be to only use the carets for parse errors,
>which is where they are the most helpful.
And preprocessor if possible
[also sometimes I would love to have an option in gcc to just
display the preprocessed input when something bad happens inside
a macro. I usually do that from hand using gcc -E, but it would be cool
if the compiler could do it automatically, ideally with carets]
> What do other compilers do? Reopening the file doesn't work for
> standard input, which I admit is an unusual case.
I think it would be reasonable to just not display the carets
if the input is not seekable. Surely qemu doesn't need carets
for once.
-Andi