Skip Navigation

The Computer Journal 1990 33(2):108-125; doi:10.1093/comjnl/33.2.108
© 1990 by British Computer Society
This Article
Right arrow Full Text (PDF)
Right arrow Alert me when this article is cited
Right arrow Alert me if a correction is posted
Services
Right arrow Email this article to a friend
Right arrow Similar articles in this journal
Right arrow Similar articles in ISI Web of Science
Right arrow Alert me to new issues of the journal
Right arrow Add to My Personal Archive
Right arrow Download to citation manager
Right arrow Search for citing articles in:
ISI Web of Science (2)
Right arrowRequest Permissions
Google Scholar
Right arrow Articles by PHILBROW, P. C.
Right arrow Articles by ATKINSON, M. P.
Right arrow Search for Related Content
Social Bookmarking
Add to CiteULike   Add to Connotea   Add to Del.icio.us  
What's this?

Events and Exception Handling in PS-algol

P. C. PHILBROW * and M. P. ATKINSON *

Department of Computing Science, University of Glasgow, Glasgow, G12 8QQ, UK

Handling exceptional circumstances is frequently the reason why an elegant and expressive algorithm becomes obscure and verbose when transcribed into a programming language. This paper reviews the exception handling facilities of existing languages and uses these to illustrate the factors influencing the design of the exception handling facilities in PS-algol. These facilities eventually materialised in the notions of system events and programmer exceptions. A description is given of event and exception handling in PS-algol.

Received February 1987. revised February 1988.

* Department of Computing Science, University of Glasgow, Glasgow, G12 8QQ


Add to CiteULike CiteULike   Add to Connotea Connotea   Add to Del.icio.us Del.icio.us    What's this?




Disclaimer:
Please note that abstracts for content published before 1996 were created through digital scanning and may therefore not exactly replicate the text of the original print issues. All efforts have been made to ensure accuracy, but the Publisher will not be held responsible for any remaining inaccuracies. If you require any further clarification, please contact our Customer Services Department.