|Re: [QUERY] A "ignorant newbie" question about compiler-writing. firstname.lastname@example.org (J. Kanze) (1997-01-30)|
|Re: [QUERY] A "ignorant newbie" question about compiler-writing. email@example.com (Mary Fernandez) (1997-02-11)|
|Re: [QUERY] A "ignorant newbie" question about compiler-writing. firstname.lastname@example.org (1997-02-16)|
|Re: [QUERY] A "ignorant newbie" question about compiler-writing. email@example.com (Norman Ramsey) (1997-02-20)|
|Re: recovery from syntax errors, was "ignorant newbie" question firstname.lastname@example.org (Jerry Leichter) (1997-02-22)|
|Re: recovery from syntax errors, was "ignorant newbie" question email@example.com (Ray Dillinger) (1997-02-22)|
|From:||Ray Dillinger <firstname.lastname@example.org>|
|Date:||22 Feb 1997 23:12:56 -0500|
|References:||97-01-258 97-02-081 97-02-090 97-02-107|
Dennis Yelle <email@example.com> wrote:
> >It seems obvious that you cannot produce a compiler that will always
> >give a correct second error message, because the compiler cannot know
> >what I actually intended in place of the first error.
Norman Ramsey wrote:
> Um, it may seem obvious, but it's not. The algorithm I described
> ``taints'' everything that could possibly depend on the first
> erroneous construct, and it refuses to issue error messages about
> tainted things. That way it can produce reliable error messages about
> other parts of your program, which don't depend on the first error.
It occurs to me that the second and subsequent errors returned from
your system as described, may result from code that was *supposed* to
depend on the code containing the first error, but which, due to the
first error did not.
Everything in the program, either does or does not depend on the part
of the program in which the error was found; but the simple fact of
the error can easily screw up your ability to determine which category
a piece of code falls into.
Return to the
Search the comp.compilers archives again.