Exception handling mechanisms have been around for more than 30 years. Nevertheless, modern exceptions systems are not very different from the early models. Programming languages designers often neglect the exception mechanism and look at it more like an add-on for their language instead of central part. As a consequence, software quality suffers as programmers feel that the task of writing good error handling code is too complex, unattractive and inefficient. We propose a new model that automates the handling of exceptions by the runtime platform. This model frees the programmer from having to write exception handling code and, at the same time, successfully increases the resilience of programs to abnormal situations.
[1]
P. Marques,et al.
Unchecked Exceptions : Can the Programmer be Trusted to Document Exceptions ?
,
2006
.
[2]
Rebecca Wirfs-Brock.
Toward Exception-Handling Best Practices and Patterns
,
2006,
IEEE Software.
[3]
Nir Shavit,et al.
Software transactional memory
,
1995,
PODC '95.
[4]
Paulo Marques,et al.
Exception Handling: A Field Study in Java and .NET
,
2007,
ECOOP.
[5]
Cecília M. F. Rubira,et al.
A comparative study of exception handling mechanisms for building dependable object-oriented software
,
2001,
J. Syst. Softw..