Exceptions and Eventflow

  1. Lookup NU author(s)
  2. Dr Christopher Holt
Author(s)Holt CM
Publication type Report
Series TitleDepartment of Computing Science Technical Report Series
Source Publication DateMarch 1999
Report Number660
Full text is available for this publication:
Exceptions historically derive from a single-threaded, imperative model of computation. Rather than including tests for the success of subsidiary operations at every procedure level using if-then-else's, it was deemed simpler to describe problems only where they arise and where they are dealt with. The catch-throw style was transferred to C++ (and then Java), and also grafted onto the I/O structures of declarative languages such as Prolog and Haskell. However, the evolution from object-oriented to event-oriented programming and the blending of this with a declarative base has led to a rather different view of computation, one which raises new questions about the relationships among events, exceptions and interrupts. This paper looks at some of these.
InstitutionDepartment of Computing Science, University of Newcastle upon Tyne
Place PublishedNewcastle upon Tyne
ActionsLink to this publication