Dony, C., "Improving Exception Handling with Object-Oriented Programming," 14th International Conference on Computer Software and Applications, 1990 Home/Search Document Details and Download
Summary Related Articles Check |
This paper is cited in the following contexts:
Portable Implementation of Continuation Operators in.. - Sekiguchi, Sakamoto.. (2001) (1 citation) (Correct)
....continuations was partly implemented in early programming languages such as PL I and Mesa [17] where execution can restart at the instruction following the one that raised an exception when the exception is captured by an exception handler. In addition, a model of exception handling is proposed [8] in which resumption contexts are first class objects and are modifiable. Our scheme can be used to implement such an exception handling mechanism on imperative languages in a portable manner. 3 Emulating Continuations This section describes how the control operators in Sect. 2 are implemented ....
Christophe Dony. Improving Exception Handling with Object-Oriented Programming. In Proceedings of the 14th IEEE computer software and application conference COMPSAC'90, pages 36--42, November 1990.
A Methodology for Adapting to Patterns of Faults - Agha, Sturman (1994) (13 citations) (Correct)
....code into an application. Goodenough introduced the idea of exceptions and exception handling in [19] Since then, many different exception handling mechanisms have been proposed. Exception handling constructs have been developed for object based languages such as Clu [24] and Ada [12] Dony [13] describes an approach for object oriented languages and its implementation in Smalltalk. In this approach, exceptions are implemented as objects much as we do. Exception handling for C is discussed in [33] A good overview of techniques proposed for other object oriented languages can be found ....
....signaled whenever an unexpected condition is encountered. An exception may be signaled either by the run time system or by the application. The former are referred to as system exceptions and the latter as user defined exceptions. Exceptions in Screed are represented as objects, as proposed in [13] for sequential object oriented languages. Although none of the other concurrent languages discussed above have taken this approach, we feel representing exceptions as objects allows for more flexible and efficient exception 18 A Methodology for Adapting to Patterns of Faults handling: all the ....
Christophe Dony. Improving Exception Handling with Object-Oriented Programming. In Proceedings of the 14th Annual International Computer Software and Applications Conference, pages 36--42, Chicago, 1990. IEEE Computer Society, IEEE.
Programming Notations for Expressing Error Recovery in a.. - Issarny (1993) (1 citation) (Correct)
....the next subsection. Finally, a set of predefined exceptions are subsumed within the mechanism. Among them, we identify exceptions related 4 Although not addressed in this paper, one might think about enriching information carried by exceptions as notably suggested for a sequential framework in [Dony90], which would lead to dissociate exception types from exception classes. 5 In the remainder of this paper, when its meaning can be deduced from the context, the term exception designates either an exception type, an exception class or an object that is an instance of an exception class. to ....
Dony (C.). -- Improving exception handling with object-oriented programming. In : Proceedings of the International Conference on Computer Languages, pp. 36--42.
High Performance Robust Computer Systems - DeVale (2001) (1 citation) (Correct)
No context found.
Dony, C., "Improving Exception Handling with Object-Oriented Programming," 14th International Conference on Computer Software and Applications, 1990
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC