Separating Exceptional Concerns
MetadataShow full item record
Traditional error handling mechanisms, including exceptions, have several weaknesses that interfere with maintainability, flexibility and genericity in software: Error code is tangled with normal code; reporting is tangled with handling; and generic code is locked into specific ways of reporting and handling errors. We need to deal with errors in a declarative way, where the concerns of errors, error reporting and error handling are separated and dealt with individually by the programmer.
CitationIn: Garcia, A.; Romanovsky, A.; Kienzle, J.; Dony, C.; Barbosa, E. [Eds.]. Proceedings of the 5th International Workshop on Exception Handling (WEH 2012): 49-51
Copyright 2012 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works.