Vis enkel innførsel

dc.contributor.authorBagge, Anya Heleneeng
dc.date.accessioned2014-12-11T14:41:17Z
dc.date.available2014-12-11T14:41:17Z
dc.date.issued2012eng
dc.PublishedIn: Garcia, A.; Romanovsky, A.; Kienzle, J.; Dony, C.; Barbosa, E. [Eds.]. Proceedings of the 5th International Workshop on Exception Handling (WEH 2012): 49-51en_US
dc.identifier.isbn978-1-4673-1767-2en_US
dc.identifier.urihttps://hdl.handle.net/1956/8918
dc.description.abstractTraditional 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.en_US
dc.language.isoengeng
dc.publisherIEEEen_US
dc.relation.ispartofseriesIEEE conference proceedingsen_US
dc.subjectAlertseng
dc.subjectExceptionseng
dc.subjectGuardingeng
dc.subjectPartialityeng
dc.subjectSeparation of Concernseng
dc.titleSeparating Exceptional Concernsen_US
dc.typeChapter
dc.typePeer reviewed
dc.date.updated2014-12-11T14:34:47Z
dc.description.versionacceptedVersionen_US
dc.rights.holderCopyright 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.en_US
dc.identifier.doihttps://doi.org/10.1109/weh.2012.6226599
dc.identifier.cristin1010821


Tilhørende fil(er)

Thumbnail

Denne innførselen finnes i følgende samling(er)

Vis enkel innførsel