Structured exception handling

ABSTRACT

In this paper, we define what exception conditions are, discuss the requirements exception handling language features must satisfy, survey and analyze existing approaches to exception handling, and propose some new language features for dealing with exceptions in an orderly and reliable way. Our objective is not solely to put forward a language proposal. It is also to analyze exception handling issues and principles in detail. The proposed language features serve to highlight exception handling issues by showing how deficiencies in current approaches could be remedied in a coherent and orderly way.

REFERENCES

• 1: Ole Johan Dahl, Structured Programming, Academic Press, Inc., Orlando, FL, 1972
• 2: Woodger, M., "On Semantic Levels in Programming." Proc. IFIP Congress 71, 1972, 402-407.
• 3: Liskov, B. H., "A Design Methodology for Reliable Software Systems," Proc. 1972 FJCC, 191-199.
• 4: Barbara H. Liskov, The design of the Venus operating system, Communications of the ACM, v.15 n.3, p.144-149, March 1972 [doi>10.1145/361268.361272]
• 5: Edsger W. Dijkstra, The structure of the “THE”-multiprogramming system, Communications of the ACM, v.11 n.5, p.341-346, May 1968 [doi>10.1145/363095.363143]
• 6: Barbara Liskov , Stephen Zilles, Programming with abstract data types, ACM SIGPLAN Notices, v.9 n.4, p.50-59, April 1974
• 7: Hoare, C. A. R. "A Note on the FOR Statement," BIT 12 (1972), 334-341.
• 8: Sevcik, D. L., et. al., "Project SUE as a Learning Experience," Proc. 1972 FJCC, 331-338.
• 9: D. L. Parnas, A technique for software module specification with examples, Communications of the ACM, v.15 n.5, p.330-336, May 1972 [doi>10.1145/355602.361309]
• 10: Parnas, D. L., "Response to Detected Errors in Well-Structured Programs," Dept. of Comp. Sci., Carnegie-Mellon University, Pittsburgh, Pa., July 1972.
• 11: Mitchell, J. G., Signals, Unpublished note, September 1973.
• 12: Lampson, B. W. , Mitchell, J. G. , and Satterthwaite, E. H., On the Transfer of Control Between Contexts, Xerox PARC, Palo Alto, Cal., undated.
• 13: Noble, J. M., "The Control of Exceptional Conditions in PL/I Object Programs," Proc. IFIP Congress 68, C78-C83.
• 14: Knuth, D. E., Structured Programming With GOTO Statements, STAN-CS-74-416, Stanford University, Palo Alto, California PB233507/3, May 1974.
• 15: Charles T. Zahn, Jr., A control statement for natural top-down structured programming, Programming Symposium, Proceedings Colloque sur la Programmation, p.170-180, April 09-11, 1974
• 16: Douglas T. Ross, The AED free storage package, Communications of the ACM, v.10 n.8, p.481-492, Aug. 1967 [doi>10.1145/363534.363546]
• 17: Solomon W. Golomb , Leonard D. Baumert, Backtrack Programming, Journal of the ACM (JACM), v.12 n.4, p.516-524, Oct. 1965 [doi>10.1145/321296.321300]
• 18: Horning, J. J. , Lauer, H. C., Melliar-Smith, P. M., Randell, B., Program Structure for Error Detection and Recovery, Computing Laboratory, Univ. of Newcastle upon Tyne, England, December 11, 1973.
• 19: C. A. R. Hoare, Parallel programming: an axiomatic approach., Stanford University, Stanford, CA, 1973
• 20: ____, AED Programmer's Guide, SofTech, Inc., Waltham, Mass. 1972.
• 21: ____, OS PL/I Checkout and Optimizing Compiler: Language Reference Manual, IBM Corp., GC 33-0009-3, 1974.
• 22: Gerald M. Weinberg, The Psychology of Computer Programming, John Wiley & Sons, Inc., New York, NY, 1985
• 23: Elliott I. Organick, The Multics System: An Examination of Its Structure, The MIT Press, 1972
• 24: Parnas, D. L., "Information Distribution Aspects of Design Methodology," Proc. IFIP Congress 71, Booklet TA-3, 26-30.
• 25: D. L. Parnas, On the criteria to be used in decomposing systems into modules, Communications of the ACM, v.15 n.12, p.1053-1058, Dec. 1972 [doi>10.1145/361598.361623]
• 26: G. V. Bochmann, Multiple exits from a loop without the GOTO, Communications of the ACM, v.16 n.7, p.443-444, July 1973 [doi>10.1145/362280.362300]
• 27: ____, The Multics Programmer's Manual, Vol. II - Reference Guide, Honeywell, Inc., AG-91A, July 1973.