A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2007; you can also visit the original URL.
The file type is
Proceedings of the 2nd workshop on Best practices in applying aspect-oriented software development - BPAOSD '07
One of the fundamental motivations for employing exception handling in the development of robust applications is to lexically separate error handling code from the normal code so that they can be independently modified. However, experience has shown that exception handling mechanisms of mainstream programming languages fail to achieve this goal. In most systems, exception handling code is interwined with the normal code, hindering maintenance and reuse. Moreover, because of limitations in thedoi:10.1145/1229485.1229486 fatcat:lsdpg67a2fghxcdklowa3n6rgy