Re: [Followup] Re: "Near Miss" error handling?

gwyn@thislove.dyndns.org (Gwyn Judd)
14 Apr 2001 17:13:30 -0400

          From comp.compilers
Related articles
"Near Miss" error handling? gwyn@thislove.dyndns.org (2001-03-27)
Re: "Near Miss" error handling? eeide@cs.utah.edu (Eric Eide) (2001-03-31)
Re: "Near Miss" error handling? joachim_d@gmx.de (Joachim Durchholz) (2001-04-04)
[Followup] Re: "Near Miss" error handling? gwyn@thislove.dyndns.org (2001-04-10)
Re: [Followup] Re: "Near Miss" error handling? Scott.Daniels@Acm.Org (Scottie) (2001-04-12)
Re: [Followup] Re: "Near Miss" error handling? gwyn@thislove.dyndns.org (2001-04-14)
Re: [Followup] Re: "Near Miss" error handling? rog@vitanuova.com (2001-04-14)
| List of all articles for this month |
From: gwyn@thislove.dyndns.org (Gwyn Judd)
Newsgroups: comp.compilers
Date: 14 Apr 2001 17:13:30 -0400
Organization: World Center for Flux Capacitor Research
References: 01-03-135 01-03-165 01-04-011 01-04-040 01-04-078
Keywords: errors, summary
Posted-Date: 14 Apr 2001 17:13:30 EDT

Scottie <Scott.Daniels@Acm.Org> said
>I suggest that you not, like Interlisp, proceed to allow execution of
>the program once corrected. DWIM scored its corrections, and if they


Absolutely. The most mine will do is signal an error and then print a
message saying what it *thinks* the user meant. This allows the user
to hopefully correct their program more easily, but the compiler will
not do any corrections by itself. The biggest bonus with this system
is that it can quite often point out several unrelated errors with one
run, without any extraneous error messages.


--
Gwyn Judd

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.