Exception handling: Expecting the unexpected

Drew, Steve; Gough, K. John

doi:10.1016/0096-0551(94)90015-9

Cited by 13 publications

(6 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…4 Some languages support both synchronous and asynchronous events (C and Ada), whereas others support synchronous only (Cϩϩ). 20 Unix supports both asynchronous and synchronous events; some socket implementations allow a message to be sent as 'out-of-band data', causing a signal to be raised when the message arrives at destination process's host. Research into event handling in message-based operating systems is illustrated by Mach 21,22 and Chorus.…”

Section: Related Workmentioning

confidence: 99%

Event Handling in the Lego System

Hughes¹

1997

Softw: Pract. Exper.

View full text Add to dashboard Cite

SUMMARYAn event is an action that alters a program's normal flow of execution. Events can be classified into asynchronous (such as the expiration of a timer or a request to terminate a process) and synchronous (for example, arithmetic and protection faults). When an event occurs during the execution of a process, specialized software is required, either in the kernel, the process, or both. This paper describes the experiences gained in the design, implementation and operation of the event handling mechanism developed for the message-based Lego kernel and distributed system running on the iAPx86 platform. The resulting implementation is a uniform communication interface, treating all events as messages, thereby maintaining Lego's send-receive paradigm. This implementation ensures that event messages follow processes that have migrated and permit the implementation of group event software. Several applications of the event handling software are presented, as is a discussion of the design tradeoffs. The paper concludes that although the basic concept of message-based event handling is well understood, a system's process naming technique can influence how events are handled in a migration and with process groups.

show abstract

Section: Related Workmentioning

confidence: 99%

Event Handling in the Lego System

Hughes¹

1997

Softw: Pract. Exper.

View full text Add to dashboard Cite

show abstract

“…Exceptions because a subject of research in their own right with the publication of Goodenough's seminal article (1975), which lead to the first proper language support for exceptions, in PL/I (Auwaerter, 1976). A summary of early developments is given in (Cristian, 1989), while the design space for exception handling mechanisms is explored in (Drew & Gough, 1994). A modern account of the fundamental concepts, design issues, and the exception handling mechanisms provided in a number of languages, is given by (Sebesta, 2006).…”

Section: Related Workmentioning

confidence: 99%

What is the meaning of these constant interruptions?

Hutton

Wright

2007

J. Funct. Prog.

View full text Add to dashboard Cite

Asynchronous exceptions, orinterrupts, are important for writing robust, modular programs, but are traditionally viewed as being difficult from a semantic perspective. In this article, we present a simple, formally justified, semantics for interrupts. Our approach is to show how a high-level semantics for interrupts can be justified with respect to a low-level implementation, by means of a compiler and its correctness theorem. In this manner we obtain two different perspectives on the problem, formally shown to be equivalent, which gives greater confidence in the correctness of our semantics.

show abstract

“…More basic research into aspects of exception detection and handling in information technology has focused largely on general approaches to exception detection, exception classification, and exception handling in respect to different types of programming language, such as functional and object-oriented programming languages [67][68][69][70][71]. Exceptions may occur on an irregular basis because of malfunctioning hardware components, because of design errors, and because of other general classes of exception [68,70].…”

Section: Exceptions and Exception Handlingmentioning

confidence: 99%

“…Once detected an appropriate exception handler needs to be invoked to resolve the exception, so that the normal flow of control may continue. An important aim of basic research into exception detection and handling has been to develop, firstly, a comprehensible program code and, secondly, reliable information systems [67,71]. In this respect, one common observation made is that the program code used to handle exceptions can be separated from the normal flow of control and stored in special exception handlers.…”

Section: Exceptions and Exception Handlingmentioning

confidence: 99%

A model of exceptions in sales-order-processing workflows

Derks

Weston

2005

Proceedings of the Institution of Mechanical Engineers, Part B:

View full text Add to dashboard Cite

A review of sales-order-processing (SOP) characteristics in assemble-to-order and make-to-stock companies is described. A logical model of three types of exception and their impacts is developed. This model is used to identify SOP requirements that need to be satisfied by next-generation workflow systems. With reference to these requirements deficiencies in current based workflow system provision based on enterprise resource planning are discussed.

show abstract

Exception handling: Expecting the unexpected

Cited by 13 publications

References 10 publications

Event Handling in the Lego System

Event Handling in the Lego System

What is the meaning of these constant interruptions?

A model of exceptions in sales-order-processing workflows

Contact Info

Product

Resources

About