Issues with exception handling in object-oriented systems

Miller, Robert; Tripathi, Anand

doi:10.1007/bfb0053375

Cited by 68 publications

(75 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This observation is also made by Miller and Tripathi, who note in [7]: "For exceptions, new functionality may need new exceptions that are not subtypes of exceptions from the parent method". Further, the authors conclude that "[...] evolutionary program development suggests exception non-conformance".…”

Section: New Functionality -New Exceptionsmentioning

confidence: 62%

“…Miller and Tripathi in [7] rightfully point out that the exception handling mechanisms in existing object-oriented languages are oriented towards implementation only and, as such, do not provide an adequate support for system development. We are interested in a mechanism supporting implementation development as well as system evolution.…”

Section: Exception Inheritance For Exception Evolutionmentioning

confidence: 99%

See 1 more Smart Citation

Supporting Evolution of Interface Exceptions

Михайлова

Romanovsky

2001

Advances in Exception Handling Techniques

View full text Add to dashboard Cite

Abstract. Interface exceptions (explicitly declared exceptions that a method can propagate outside) are an inherent part of the interface describing the behaviour of a particular class of objects. Evolution of system behaviour is thus necessarily accompanied by and reflected in the evolution of interface exceptions. While evolution of normal system behaviour is adequately supported by various language mechanisms, such as subtyping and inheritance, few contemporary object-oriented programming languages offer support for the evolution of interface exceptions. Some languages permit specialising and deleting interface exceptions while subtyping, but none of them provides an adequate support for adding exceptions. In this paper we propose two solutions for dealing with additional exceptions introduced while system evolution. To solve the problem of non-conforming interfaces resulting from the addition of new exceptions in a development step, the first proposal uses rescue handlers and the second one employs the forwarding technique.

show abstract

Section: New Functionality -New Exceptionsmentioning

confidence: 62%

Section: Exception Inheritance For Exception Evolutionmentioning

confidence: 99%

Supporting Evolution of Interface Exceptions

Михайлова

Romanovsky

2001

Advances in Exception Handling Techniques

View full text Add to dashboard Cite

show abstract

“…While the above discussion is somewhat particular to concept-oriented programming, the issue also occurs to some degree with object-orientation [7]. For example, when specifying the exceptions of an interface or superclass in Java, one has to either declare a wide range of exceptions, providing less detail to the users, and possibly forcing them to deal with lots of exceptions that may never occur; or declare few or no exceptions, restricting the use of exceptions in the implementation or subclass.…”

Section: Element Get(map Map Key Key)mentioning

confidence: 99%

Separating exceptional concerns

Bagge¹

2012

2012 5th International Workshop on Exception Handling (WEH)

View full text Add to dashboard Cite

Abstract-Traditional error handling mechanisms, including exceptions, have several weaknesses that interfere with maintainability, flexibility and genericity in software: Error code is tangled with normal code; reporting is tangled with handling; and generic code is locked into specific ways of reporting and handling errors. We need to deal with errors in a declarative way, where the concerns of errors, error reporting and error handling are separated and dealt with individually by the programmer.

show abstract

“…It conflicts with some object oriented design paradigms [28] because implementation information may be exposed to objects earlier in the call chain that were interacting with an abstract interface. Using a class hierarchy for exceptions is useful in this case because components at high abstraction levels can interact with abstract exceptions.…”

Section: Improved Error Reportingmentioning

confidence: 99%

Exception Handling in the Choices Operating System

David

Carlyle

Chan

et al. 2006

Advanced Topics in Exception Handling Techniques

View full text Add to dashboard Cite

Abstract. Exception handling is a powerful abstraction that can be used to help manage errors and support the construction of reliable operating systems. Using exceptions to notify system components about exceptional conditions also reduces coupling of error handling code and increases the modularity of the system. We explore the benefits of incorporating exception handling into the Choices operating system in order to improve reliability. We extend the set of exceptional error conditions in the kernel to include critical kernel errors such as invalid memory access and undefined instructions by wrapping them with language-based software exceptions. This allows developers to handle both hardware and software exceptions in a simple and unified manner through the use of an exception hierarchy. We also describe a catch-rethrow approach for exception propagation across protection domains. When an exception is caught by the system, generic recovery techniques like policy-driven micro-reboots and restartable processes are applied, thus increasing the reliability of the system.

show abstract

Issues with exception handling in object-oriented systems

Cited by 68 publications

References 12 publications

Supporting Evolution of Interface Exceptions

Supporting Evolution of Interface Exceptions

Separating exceptional concerns

Exception Handling in the Choices Operating System

Contact Info

Product

Resources

About