Why Using return codes? - Purpose & Use Cases

The Big Idea

What if your program could tell you exactly when and why it fails, instead of leaving you guessing?

The Scenario

Imagine you write a program that calls many functions, but you have no way to know if each function worked correctly or failed. You just guess or check manually by printing messages everywhere.

The Problem

This manual way is slow and confusing. You might miss errors, or your program might continue running with wrong data. It's like driving blindfolded, hoping you don't crash.

The Solution

Using return codes lets each function tell you exactly if it succeeded or failed. Your program can then decide what to do next, like fixing the problem or stopping safely.

Before vs After

✗ Before

void doTask() {
    // no feedback if error
    performStep1();
    performStep2();
}

✓ After

int doTask() {
    if (performStep1() != 0) return -1;
    if (performStep2() != 0) return -2;
    return 0;
}

What It Enables

It enables your program to handle errors clearly and safely, making your code more reliable and easier to fix.

Real Life Example

Think of a vending machine: it returns a code if it's out of snacks or if the payment failed, so it can show the right message or refund your money.

Key Takeaways

Manual error checking is confusing and risky.

Return codes give clear success or failure signals.

This helps programs handle problems safely and predictably.