exception handling

(redirected from Error handler)

exception handling

[ek′sep·shən ‚hand·liŋ]
(computer science)
Programming techniques for dealing with error conditions, generally without terminating execution of the program.
(control systems)
The actions taken by a control system when unpredictable conditions or situations arise in which the controller must respond quickly.
McGraw-Hill Dictionary of Scientific & Technical Terms, 6E, Copyright © 2003 by The McGraw-Hill Companies, Inc.

exception handling

The ways in which an application responds to abnormal conditions, such as a divide-by-zero calculation or other type of irregular processing. Built into the programming language or the hardware itself, exception handling is generally resolved without the user's knowledge, although that is not always the case. Contrast with "error handling," where routines written by the programmer are able to inform the user of erroneous input or other irregular conditions. See error handling.
Copyright © 1981-2019 by The Computer Language Company Inc. All Rights reserved. THIS DEFINITION IS FOR PERSONAL USE ONLY. All other reproduction is strictly prohibited without permission from the publisher.
References in periodicals archive ?
Initially, an error handler is defined so the code can exit without the user realizing there's a problem, and zero (0) is assigned for the default return value.
In Example 2, testing the error handler requires the stub for uploadingData() to have at least one case that returns a true condition.
An error handler that determines the nature of any errors in the XML document and then acts accordingly.
SoftBase's Database Rely, Data Generation Facility, Database Attach and Query Error Handler assist enterprise companies to maintain data integrity, handle batch process errors, and ensure that critical processes remain running.
In Chimera, a generic assembly language timing error handler was created.
Therefore, an error handler routine (analogous to the event handler) is called when an error condition arises during a simulation run.
We grouped the causes of the crashes into the following categories: pointer/array errors, not checking return codes, input functions, sub-processes, interaction effects, bad error handler, signed characters, race conditions, and currently undetermined.