Browse Prior Art Database

Error Stack for an Error Handling Interface

IP.com Disclosure Number: IPCOM000113959D
Original Publication Date: 1994-Oct-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 2 page(s) / 27K

Publishing Venue

IBM

Related People

Forman, IR: AUTHOR [+2]

Abstract

Handling errors within an object oriented system is not always easy. Developers must report and handle error conditions, and users must have enough information to diagnose the problem. In additon, errors may be nested deeply within a system. Disclosed is a partial solution to this problem.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 100% of the total text.

Error Stack for an Error Handling Interface

      Handling errors within an object oriented system is not always
easy.  Developers must report and handle error conditions, and users
must have enough information to diagnose the problem.  In additon,
errors may be nested deeply within a system.  Disclosed is a partial
solution to this problem.

      The proposed partial solution is to create an error class and
an error stack class.  As errors are encountered, information about
them is stored in an error object and placed on the error stack.  The
stack supports methods to report, examine, and handle errors.  Error
handlers can then look at the errors on the top of the stack, which
may be just symptoms of the root problem.  In addition, they may also
look at errors below the top of the stack, which may provide better
information about failures on the top of the stack.  When errors are
resolved, they may be popped off of the stack and discarded.  This is
an improvement over error logs, which may be needlessly cluttered
with error conditions which were previously solved.