Exception Handling in Software Development: A Comprehensive Analysis

This article is the first in the "Abnormal Thinking Records" series, focusing on exception handling approaches in software development. The author systematically explores the distinction between "errors" (fundamental issues like memory insufficiency that cannot be recovered) and "exceptions" (predictable problems during program execution that can be handled).

The article begins by clarifying terminology based on Java and C++ standards: errors represent unrecoverable issues like OutOfMemoryError or StackOverflowError, while exceptions represent recoverable problems like NullPointerException or SQLException. C++ further categorizes exceptions into logic_error (detectable before execution) and runtime_error (detectable only during execution).

The core content examines five major categories of exception handling approaches:

1. Global Error Codes: Including C's errno (thread-local in modern systems), OpenSSL's error stack (providing call frame information), and VB/VBA's Err object (with IDE integration). The article notes challenges with coroutine environments where errno may not be properly preserved during context switching.

2. Return Values as Errors: Covering libcurl's CURLcode enumeration, Go's multiple return values with error, Rust's Result type with the ? operator, C++11's std::error_code with error_category, Google's absl::StatusOr, C++23's std::expected, and Boost.Outcome. Each approach's advantages and limitations are analyzed.

3. Parameter-Based Error Collection: Including std::filesystem's error_code parameters, Google's protobuf::RpcController, and Protobuf's MultiFileErrorCollector pattern for callback-based error handling.

4. Language-Level Exception Support: Examining C++, JavaScript, Java, C#, and Delphi's exception mechanisms. The article discusses how these languages provide call stack information and unified error handling models, with C++23 adding stack trace support to the standard library.

5. Operating System Support: Detailing Windows' Structured Exception Handling (SEH) and Vectored Exception Handling (VEH), which provide OS-level exception handling that any language can utilize through Win32 APIs.

The article concludes that different approaches suit different scenarios, and the choice depends on factors like performance requirements, error code management needs, and whether the system follows object-oriented design principles.