The concrete error callbacks provide the greatest level of detail: their names indicate the kind of error condition detected. This makes it possible to treat different errors differently.
The operation level error callback is executed whenever an error condition is detected during the execution of that operation. In a extending of this kind of error callback, you can adjust the default action for all the concrete error callbacks in this operation. The single socket level error callback is executed whenever any operation detects any error condition. In a extending of this error callback, you can adjust the default action for all concrete and operation level error callbacks.
The means for adjusting the behaviour is in all cases to execute abort (probably abort(# leave L #)), continue, or fatal, and the semantics of these imperatives are the semantics of the concrete error callbacks.
Error callback extendings take precedence like this, in ascending order: concrete level, operation level, socket level. This means that the higher level specifies a default, and the more concrete level may override this default by executing continue, abort, or fatal.
| Process Libraries - Reference Manual | © 1994-2002 Mjølner Informatics |
[Modified: Friday October 20th 2000 at 14:22]
|