https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85664
Bug ID: 85664
Summary: Don't ask questions if tere's no way to answer
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: gcc at mailed dot e4ward.com
Target Milestone: ---
(gcc (Ubuntu 7.3.0-16ubuntu3) 7.3.0)
How is the weather today?
All readers who are now irritated that they can't very well go and react to a
bug report solely to write about the weather, will realise that I should not
have asked about the weather somewhere where the reader can't answer me. This
is a standard for any publication: Don't ask the audience a question if they
have no way to reply.
Yet, every time I mistype a name - which with my co-ordination is a rather
frequent occurrence - GCC will now ask me: "; did you mean ‘<alternative>’?".
I find offering an alternative an interesting concept. I haven't even looked up
yet how to switch it off as it's usually correct. (I do get the impression the
guesses are about the fairly obvious, which is when they are fairly obvious to
me as well, suggesting this doesn't add much.) But they are suggestions, not
questions.
A development environment can ask question i this situation because, when the
user replies by activating the confirm function, it can actually modify the
code it's holding. A stand-alone compiler should not ask questions.
Could this please be reworded?
Bye,
Mysha
