https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81328
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2017-07-06
CC| |ebotcazou at gcc dot gnu.org
Summary|Wrong order of error |error messages not in
|messages |expected order
Ever confirmed|0 |1
Severity|normal |enhancement
--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> GNAT provides an error list for my erroneous input in wrong order.
No, it's not "wrong", it's just the natural order of the source code, which is
perfectly reasonable.
> I sent a minimized code where this is not a problem, but I got this GNAT
> behavior in real code, what lead me to try to first fix the first error
> (which in reality was caused by the second error), but it was unexpected
> that to fix the first error I first need to fix the second error.
And you didn't manage to fix your code in the end?
> The output order of compilation errors should be such that the programmer
> would be able to fix the errors in the order of compiler output, rather than
> to make the programmer to guess that he needs first look into the next error.
This sounds interesting, albeit probably a lot of work so will never happen.
