Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| Error reporting/recovery bourguet@my-deja.com (Jean-Marc Bourguet) (2000-04-05) |
| Re: Error reporting/recovery iank@bearcave.com (2000-04-11) |
| Re: Error reporting/recovery grosch@cocolab.de (2000-04-11) |
| Re: Error reporting/recovery bourguet@my-deja.com (Jean-Marc Bourguet) (2000-04-14) |
| Re: Error reporting/recovery bourguet@my-deja.com (Jean-Marc Bourguet) (2000-04-14) |
| Re: Error reporting/recovery rod.bates@wichita.boeing.com (Rodney M. Bates) (2000-04-14) |
| Re: Error reporting/recovery nr@labrador.eecs.harvard.edu (2000-04-16) |
| Re: Error reporting/recovery j.coulmance@itecor-software.com (Jocelyn Coulmance) (2000-04-20) |
| Re: Error reporting/recovery pnyq@my-deja.com (2000-05-08) |
| From: | nr@labrador.eecs.harvard.edu (Norman Ramsey) |
| Newsgroups: | comp.compilers |
| Date: | 16 Apr 2000 18:27:42 -0400 |
| Organization: | Harvard University |
| References: | 00-04-053 00-04-074 00-04-090 00-04-115 |
| Keywords: | parse, errors |
Rodney M. Bates <rod.bates@wichita.boeing.com> wrote:
>I developed the habit of giving most of the fields in my data
>structure a reserved value which means it is unknown or meaningless
>because of earlier errors (, or possibly for some other reason).
>Then every error check looks for such values in any of the data it
>uses and does not generate error messages if there are any unknown
>values.
This technique has been rediscovered over and over.
<blatant plug>
For an example of how a polymorphic language can help enforce this
discipline, see
Ramsey, Norman. 1999. Eliminating spurious error messages using
exceptions, polymorphism, and higher-order functions. Computer
Journal, 42(5):360--372.
http://www.eecs.harvard.edu/~nr/pubs/error-abstract.html
</blatant plug>
Return to the
comp.compilers page.
Search the
comp.compilers archives again.