To get the most out of this manual, you need to know that ABL has two error handling models and this manual is organized around describing these models separately. Your interest in either or both of these models is your best guide to understanding which parts of the manual will be useful to you. The minimal definitions of the models below will guide you as you get started:
Traditional error handling — All error handling features included in ABL before the release of OpenEdge Release 10.1C comprise the ABL's original error handling model. To allow useful comparisons between original and newer error handling, the documentation refers to the original error handling features and techniques as traditional error handling.
Traditional error handling is still a viable error handling model and comprises the foundation of the new error handling model. In fact, original and new error handling features seamlessly coexist and interoperate in ABL code.
Structured error handling — Introduced in OpenEdge Release 10.1C, structured error handling builds on existing error handling features. It represents errors as class-based objects that can be trapped with custom error handlers and easily passed from a called context to a calling context. Structured error handling is sometimes referred to as try and catch functionality and is a common feature in object-oriented programming languages.
The content of this chapter is essential for all users. The rest of the chapters are likely to interest you depending on which of the following groups you belong to:
Traditional error handling — All error handling features included in ABL before the release of OpenEdge Release 10.1C comprise the ABL's original error handling model. To allow useful comparisons between original and newer error handling, the documentation refers to the original error handling features and techniques as traditional error handling.
