Robert Miller and Anand Tripathi. Issues with exception handling in objectoriented systems. In ECOOP, pages 85--103, 1997.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....2 4 of this work appeared in [Romanovsky et al. 1998a] See [A. Romanovsky et al. 1998b] object oriented (OO) or object based, the object oriented paradigm adds a new complication to system design since several aspects of this paradigm conflict with the principle of structured exception handling [Miller Tripathi 1997]. Finally, real time requirements cause added difficulties with regard to modelling the real time behaviour of a system and to handling time related exceptions properly. Therefore, developing a general exception handling approach that can effectively cope with distribution, object orientation, and ....

R. Miller and A. Tripathi, "Issues with Exception Handling in ObjectOriented Systems," in Proc. ECOOP'97 - Object-Oriented Programming, pp.85-103, LNCS1241, Finland, 1997.

....showing that it is possible to meet al..l except one of its guidelines by implementing it using the error value model in the spreadsheet paradigm. 2. 3 Exception Handling in Other Applicative Languages Most research on exception handling has been in imperative [11, 17, 31, 68] object oriented [14, 34, 48, 66], and functional languages [2, 19, 43, 60] The approaches to exception handling in the imperative and object oriented paradigms usually accomplish their purposes in part by allowing Yemeni and Berry named it the replacement model. We use the phrase replacement value model in this paper ....

R. Miller and A. Tripathi, "Issues with Exception Handling in Object-Oriented Systems," European Conference on Object-Oriented Programming, Jyvaskyla, Finland, June 9-13, 1997.

....:Canvas Artist Picture Figure 23. Modified Linguistic model 3.3.3 Adding exception handling The issue of handling exceptions is actually a separate field of research with a number of open issues. Combining object oriented modelling and exception handling results in a number of anomalies, see e.g. [Miller, Tripathi, 1997]. The relevancy of exception handling for this case study is that exceptions tend to transcend the different components of user interface architectures. An extension of the CD system augmented with a picture of the artist, as described in above, would be to retrieve the picture from a remote ....

Robert Miller, Anand Tripathi, "Issues with Exception Handling in Object-Oriented Systems", in: M. Aksit, S. Matsuoka (eds.), ECOOP'97 Proceedings, Springer Verlag, 1997, pp. 85-103

....in this paper differs from these efforts as it focuses on reasons why exception structure degrades, and investigates a disciplined design technique to alleviate the problems causing degradation. More closely related to the problems discussed in this paper is an analysis by Miller and Tripathi [10] of why it is difficult to design exceptions in object oriented systems. However, their analysis focuses on conceptual clashes between object orientation and exception handling, such as abstraction, encapsulation, modularity and inheritance, rather than on the realities of programming with ....

R. Miller and A. Tripathi. Issues with exception handling in object-oriented systems. In Proc. of ECOOP'97, LNCS 1241, pages 85--103. Springer-Verlag, June 1997.

....an invocation is executed substituting the operation code at the place where inner is declared. The inner mechanism also allows a subclass to extend or augment the exception handling of the parent class. Using the inner mechanism for this purpose requires a good understanding of the pattern code [Miller and Tripathi, 1997]. 4.12 Exception Handling in Arche Arche [Issarny, 1993] is a concurrent object oriented language which makes a clear distinction between type (a description of an interface) and class (an implementation of a type) Exceptions are data objects in Arche. Exception interface is supported, but ....

Miller, R., Tripathi, A., Issues with Exception Handling in Object-Oriented Systems, Proceedings of ECOOP'97, LNCS 1241, 85-103 (1997).

....systems can evolve (Section 3.1) it is clear that these ways of inheriting, redeclaring and removing interface exceptions are too restrictive and should be relaxed to support other forms of behaviour evolution as well. 8 3. 5 Exception Inheritance for Exception Evolution 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 ....

....interface exception redeclaration. As demonstrated by this example, what we would like to have is more flexibility, enabling the kind of interface exception redeclaration when a subtype method can signal completely new exceptions. 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 . Fortunately, this apparently desirable exception non covariance ....

[Article contains additional citation context not shown here]

R. Miller and A. Tripathi. Issues with exception handling in object-oriented systems. In M. Aksit and S. Matsuoka, editors, ECOOP '97 --- Object-Oriented Programming 11th European Conference, Jyvaskyla, Finland, volume 1241 of Lecture Notes in Computer Science, pages 85--103. Springer-Verlag, New York, NY, June 1997.

....programs. Many of the problems we have identified with exception structure degradation, such as exceptions that arise because of the implementation path chosen, are not discussed in the literature. More closely related to the problems discussed in this paper is an analysis by Miller and Tripathi [11] of why it is difficult to design exceptions in object oriented systems. However, their analysis is focused on conceptual clashes between object orientation and exception handling, such as abstraction, encapsulation, modularity and inheritance, rather than on the realities of programming with ....

R. Miller and A. Tripathi. Issues with exception handling in object-oriented systems. In Proceedings of the 11th European Conference on Object-Oriented Programming, volume 1241 of Lecture Notes in Computer Science, pages 85--103. Springer-Verlag, June 1997.

....borrowed from them. We give a more elaborate literature survey in Section 5. Exceptions have been studied within a number of communities: programming languages, software engineering, databases, and artificial intelligence. Miller Tripathi define an exception as an abnormal computational state [18]. An abnormal state may result from an error (illegal) a deviation (legal, but undesirable) a notification (invalidating a previous assumption) or an idiom (legal, but rare) Miller Tripathi then go on to study the case of errors. By contrast, we concentrate on the other three kinds of ....

Robert Miller and Anand Tripathi. Issues with exception handling in object-oriented systems. In European Conference on Object-Oriented Programming, volume 1241 of LNCS, pages 85--103, 1997.

....classification of exceptions into exception type hierarchies. These hierarchies introduce the possibility of writing general handlers that may implicitly catch a subset of more specific exceptions. This implicit catching of exceptions can complicate the development and evolution of robust classes [MT97]. To investigate whether information about the flow of exceptions might help a developer fill in these gaps, we have built a tool, called Jex, to analyze exception flow in Java source code. When applied to a Java class, Jex determines the precise types of exceptions that may be raised at each ....

....in Section 6. Section 7 summarizes the paper. 2 Previous Work Goodenough [Goo75] introduced the exception handling concepts in common use today. To provide a common basis for discussion, we begin with a brief review of these concepts and the related terminology as defined by Miller and Tripathi [MT97]. An exception is an abnormal computation state. An exception occurrence is an instance of an exception. An exception is raised when the corresponding abnormal state is detected. Signaling an exception by an operation (or a syntactic entity such as a statement or block) is the communication ....

[Article contains additional citation context not shown here]

Robert Miller and Anand Tripathi. Issues with exception handling in object-oriented systems. In Mehmet Aksit and Satoshi Matsuoka, editors, ECOOP'97---Object-Oriented Programming, 11th European Conference, volume 1241 of Lecture Notes in Computer Science, pages 85--103. Springer, June 1997.

....from several objects of the same type. Such resolution is however only suitable for a limited form of concurrency. Wellings and Burns [Wellings Burns 1997] have recently shown how Ada 95 can be used to implement atomic actions, but without addressing exceptions concurrently raised. The work in [Miller Tripathi 1997] discusses many important problems arising when exception handling mechanisms are used in object oriented systems. It summarises previous research and presents new unsolved problems. The authors concluded that this is a difficult and delicate task because exception handling mechanism cannot be ....

R. Miller and A. Tripathi, "Issues with Exception Handling in Object-Oriented Systems," in Proc. ECOOP'97 --- Object-Oriented Programming, pp.85-103, LNCS-1241, Finland, 1997.

.... which has shown that exception handling is an effective technique only when associated 2 with the appropriate structuring mechanisms, such as Coordinated Atomic Actions (CA actions) Xu 95] Although exception handling and object oriented languages raise some conflicts, as it was discussed in [Miller 97] these conflicts exist mainly during the late phases of the lifecycle and not at the early phases which is the main focus of this paper. In our opinion, some of the issues mentioned in [Miller 97] would cease to exist if a structured approach, which incorporates exception handling right from the ....

....exception handling and object oriented languages raise some conflicts, as it was discussed in [Miller 97] these conflicts exist mainly during the late phases of the lifecycle and not at the early phases which is the main focus of this paper. In our opinion, some of the issues mentioned in [Miller 97] would cease to exist if a structured approach, which incorporates exception handling right from the early phases of the software development, is adopted for the specification of objects and their cooperations. Related work in this area has been scarce, but most of this work associates exception ....

[Article contains additional citation context not shown here]

R. Miller, A. Tripathi. "Issues with Exception Handling in Object-Oriented Systems". Proceedings of 11th European Conference on Object-Oriented Programming (ECOOP'97). Jyväskylä, Finland. Lecture Notes in Computer Science 1241. Eds. M. Aksit, S. Matsuoka. Springer-Verlag. Berlin, Germany. 1997. pp. 85-103

....from several objects of the same type. Such resolution is however only suitable for a limited form of concurrency. Wellings and Burns [Wellings Burns 1997] have recently shown how Ada 95 can be used to implement atomic actions, but without addressing exceptions concurrently raised. The work in [Miller Tripathi 1997] discusses many important problems arising when exception handling mechanisms are used in object oriented systems. It summarises previous research and presents new unsolved problems. The authors concluded that this is a difficult and delicate task because exception handling mechanism cannot be ....

R. Miller and A. Tripathi, "Issues with Exception Handling in ObjectOriented Systems," in Proc. ECOOP'97 --- Object-Oriented Programming, pp.85-103, LNCS1241, Finland, 1997.

....approaches exist. Secondly, although most existing distributed systems are to some extent object oriented (OO) or object based, the object oriented paradigm adds a new complication to system design since several aspects of this paradigm conflict with the principle of structured exception handling [Miller Tripathi 1997]. Thirdly, real time requirements cause further difficulties with regard to modelling the real time behaviour of a system and to handling time related exceptions properly. Therefore, developing a general exception handling approach that can effectively cope with distribution (and concurrency) ....

R. Miller and A. Tripathi, "Issues with Exception Handling in Object-Oriented Systems," in Proc. ECOOP'97 --- Object-Oriented Programming, pp.85-103, LNCS-1241, Finland, 1997.

No context found.

Robert Miller and Anand Tripathi. Issues with exception handling in objectoriented systems. In ECOOP, pages 85--103, 1997.

No context found.

Robert Miller and Anand Tripathi. Issues with exception handling in object-oriented systems. In S. Matsuoka M Aksit, editor, ECOOP'97 Proceedings, volume 1241 of Lecture Notes in Computer Science. Springer Verlag, 1997.

No context found.

Robert Miller and Anand Tripathi. Issues with exception handling in object-oriented systems. In Object-Oriented Programming, 11th European Conference (ECOOP), pages 85--103, 1997.

No context found.

Robert Miller, Anand Tripathi. Issues with Exception Handling in ObjectOriented Systems. In Proceedings of the European Conference on Object-Oriented Programming (ECOOP), Jyvaskyla, June 1997. Published as Lecture Notes in Computer Science (LNCS) 1241:85-103, Springer-Verlag, 1997.

No context found.

Robert Miller and Anand Tripathi. Issues with exception handling in object-oriented systems. In Object-Oriented Programming, 11th European Conference (ECOOP), pages 85--103, 1997.

No context found.

R. Miller and A. Tripathi, Issues with exception handling in object-oriented systems, In Proceedings of 97 ECOOP, 1997

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