Course contentsShow
← Software Engineering
Lesson 1085 of 1,93333. Error Handling and ResilienceFree lesson

Error Handling Philosophies: Return Codes vs Exceptions

Compare error handling approaches and understand when to use return codes, exceptions, or result types.

Error Handling Philosophies: Return Codes vs Exceptions

You'll learn: How to choose between return codes, exceptions, and result types when signaling errors in your code.

The Core Question

When something goes wrong in your code, how should you communicate it? Different programming paradigms offer different answers, and choosing the right approach affects your code's clarity, safety, and maintainability.

Return Codes: The Explicit Contract

Return codes force callers to check for error conditions explicitly. Functions return special values (like -1, null, or error codes) to signal problems.

Advantages:

  • Predictable control flow—no jumping around
  • Performance: no stack unwinding overhead
  • Visible in function signatures: you know errors can happen
  • Works in all languages

Disadvantages:

  • Easy to ignore (forget to check the return value)
  • Clutters happy-path code with error checks
  • Can't signal errors from constructors or operators

Exceptions: Separation of Concerns

Exceptions let you throw errors that automatically propagate up the call stack until caught, separating error handling from normal logic.

Advantages:

  • Clean happy-path code
  • Impossible to silently ignore
  • Works from any context (constructors, operators)
  • Natural for truly exceptional situations

Disadvantages:

  • Hidden control flow—harder to predict execution paths
  • Performance cost when thrown
  • Can be overused for non-exceptional cases

Result Types: The Modern Hybrid

Languages increasingly offer Result or Either types that explicitly wrap success or failure, combining explicit contracts with type safety. The compiler forces you to handle both cases.

When to Use What

  • Return codes: Performance-critical paths, C interop, expected frequent errors
  • Exceptions: Rare, truly exceptional conditions you can't handle locally
  • Result types: When available, for errors that are part of normal operation

Key Takeaway: Use return codes or result types for expected errors in your control, exceptions for unexpected failures—and always make error handling visible and deliberate.