On Tuesday, 9 December 2014 at 03:14:23 UTC, ketmar via
Digitalmars-d wrote:
somehow Walter can't accept that after emiting the first error
compiler
is in undefined state, and trying to pretend that it is in
well-defined
state or guess what well-defined state must be is a nonsense.
A well-designed language allows to recover from errors with good
probability and thus give simultaneous useful error reports for
multiple parts of the program. Sure, you always need the first
error message, but having other useful error messages is a
benefit as long as the probability of recovery is high enough.
