@techreport{TR-IC-06-22,
  number = {IC-06-22},
  author = {Fernando Castor Filho and Alessandro Garcia and
            Cec{\'{\i}}lia Mary F. Rubira},
  title = {Implementing Modular Error Handling with Aspects:
           Best and Worst Practices},
  month = {November},
  year = {2006}, 
  institution = {Institute of Computing, University of Campinas},
  note = {In English, 18 pages.
    \par\selectlanguage{english}\textbf{Abstract}
       One of the fundamental motivations for employing exception
       handling in the development of robust applications is to
       lexically separate error handling code so that the latter and
       the normal code can be independently modified.  Also, this
       scheme makes it possible for the normal code to be reused
       across various applications, using different error handling
       strategies.  Since error handling is an inherently crosscutting
       concern, it is usually assumed that it can be better
       modularized by the use of aspect-oriented programming (AOP)
       techniques. However, recent studies argue that the ad hoc use
       of AOP can be detrimental to the quality of a system. When
       applying AOP to modularize exception handling, developers need
       to follow clear and simple practices in order to obtain a
       well-structured system design. If developers do not receive
       proper guidance, software systems whose exceptional behavior is
       modularized through aspects can exhibit problems, such as
       unexpected flows of control and swallowed exceptions, that stem
       from poorly designed/implemented error handling code. In this
       paper, we address this problem by providing some
       design/implementation guidance regarding the use of AOP to
       modularize exception handling. We propose a classification for
       error handling code based on the factors that we found out have
       more influence on its aspectization. Moreover, we present a
       scenario catalog comprising combinations of these factors and
       analyze how these scenarios positively or negatively affect the
       task of aspectizing exception handling.
  }
}