This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
research:exceptions [2006/11/09 15:19] stijnm Naming >> research/ambientrefs.changes |
research:exceptions [2009/11/30 17:18] (current) dharnie |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ===== Ambient-Oriented Exception Handling ===== | ||
+ | [[http:// | ||
+ | {{ research: | ||
+ | |||
+ | Exception handling mechanisms have become an essential tool for software development. Since exceptions are propagated automatically by the language support, methods need to be aware only of the particular exceptions they can handle locally. This degree of obliviousness is particularly useful in a context where exceptions are bound to arise not only to report logical errors but also as a response to environmental failures (e.g. long-lasting disconnection). | ||
+ | |||
+ | == Motivation == | ||
+ | |||
+ | The motivation for an ambient-oriented exception handling mechanism stems from the fact that traditional try-catch-based exception handling mechanisms cannot be reconciled with a programming model based on non-blocking communication as prescribed by the [[: | ||
+ | |||
+ | - **Loss of Handling Context**: Traditionally, | ||
+ | - **Concurrent Exceptions**: | ||
+ | - **Implicit Dependencies**: | ||
+ | |||
+ | == Design == | ||
+ | The design of the exception handling model is closely coupled with the design of the [[Wp> | ||
+ | |||
+ | == Implementation == | ||
+ | <note warning> | ||
+ | |||
+ | == Further Reading == | ||
+ | // |