How to replace failure by a list of successes
Proc. of a conference on Functional programming languages and computer architecture
An axiomatic treatment of exception handling in an expression-oriented language
ACM Transactions on Programming Languages and Systems (TOPLAS)
Communications of the ACM
Exception handling: issues and a proposed notation
Communications of the ACM
An Exception Handling Construct for Functional Languages
ESOP '88 Proceedings of the 2nd European Symposium on Programming
Exception Handling in the Spreadsheet Paradigm
IEEE Transactions on Software Engineering - special section on current trends in exception handling—part II
EDO: Exception-directed optimization in java
ACM Transactions on Programming Languages and Systems (TOPLAS)
| Hi-index | 0.00 |
Constructs for expressing exception handling can greatly help to avoid clutter in code by allowing the programmer to separate the code to handle unusual situations from the code for the normal case. The author proposes a new approach to embed exception handlers in functional languages. The proposed approach discards the conventional view of treating exceptions, as a means of effecting a control transfer; instead, exceptions are used to change the state of an object. The two types of exceptions, terminate and resume, are treated differently. A terminate exception, when raised, is viewed as shielding the input object. On the other hand, a resume exception designates the input object as curable and requires the immediate application of a handler function. This approach enables the clean semantics of functions raising exceptions without associating any implementation restriction and without loss of the referential transparency and the commutativity properties of functions.