https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85664
--- Comment #2 from Mysha <gcc at mailed dot e4ward.com> ---
Well, Jonathan Wakely, I hear there's not enough love to go round.
But other than that: Yes, that is indeed one case of the compiler asking a
question where it shouldn't. And I like the approach of replacing it with
something like:
#include <foo.h> defines std::foo.
Indeed, I do have the impression that messages aren't as terse as they used to
be. Informative, but not really terse. And this would seem a nice short
alternative.
Another one case is the result from compiling program test.c:
inf main(){}
"
test.c:1:1: error: unknown type name ‘inf’; did you mean ‘int’?
inf main(){}
^~~
int
"
I don't know how many more unanswerable questions there are in GCC, but
reactions suggest that these informative messages with questions are not an
option, but rather the normal output. In that case, I'd rather have --terse;
just the error messages, not the informative additions. (I get a lot of these,
and with four lines per error I run our of console lines after some 17 typos.)
But for the direct case: While the other one also would like to see the wording
changed, that one is about the verbosity; what I'm after are the questions. If
there's no checksum in those files, I figure I can just hexedit them, but I'd
prefer a proper solution to that.
Bye
Mysha
