Abstract | ||
---|---|---|
Nowadays, nearly every mainstream programming language includes air exception handling mechanism. Basically, the variety of these mechanisms can be devided in two groups according to their handling models: Mechanisms which support exception termination and those which support resumption. Even though resumption was still an attractive alternative to termination Jar the first exception handling mechanisms in the 1980s, it has nearly been displaced completely in contemporary languages by termination. Sortie reasons for this trend will be reviewed in this work But in our opinion, they do not justify to reject resumption completely. To the contrary, resumption can simplify some tasks extremely while still being implementable with reasonable effort. To show this, we discuss some basic concepts of how a resumption mechanism should be designed in general and propose new syntactical constructs to support these concepts. Based on these concepts, we describe the implementation of a prototypical precompiler for Java supporting exception handling with resumption. In fact, the mechanism implemented in tire precompiler not only extends, but completely subsumes the Java mechanism, for it is capable of both, termination and resumption. |
Year | Venue | Keywords |
---|---|---|
2005 | PLC '05: Proceedings of the 2005 International Conference on Programming Languages and Compilers | flexible exception handling, Java, resumption, prototypical implementation, precompiler |
Field | DocType | Citations |
Programming language,Computer science,Exception handling,Java | Conference | 2 |
PageRank | References | Authors |
0.47 | 2 | 2 |
Name | Order | Citations | PageRank |
---|---|---|---|
Alexander Gruler | 1 | 158 | 8.30 |
Christian Heinlein | 2 | 2 | 0.47 |