Why Using errno in C? - Purpose & Use Cases

The Big Idea

What if your program could tell you exactly why it failed, every time?

The Scenario

Imagine you write a program that opens a file. If the file doesn't exist or you don't have permission, your program just crashes or behaves unpredictably without telling you why.

The Problem

Without a clear way to check errors, you must guess what went wrong. Manually checking every function's return value and guessing the cause is slow and confusing. It's like trying to fix a broken machine without knowing which part failed.

The Solution

The errno variable in C tells you exactly what error happened after a function fails. It's like a helpful signpost pointing to the problem, so you can handle errors clearly and fix issues faster.

Before vs After

✗ Before

if (open("file.txt", O_RDONLY) == -1) {
    // No info about error
    printf("Failed to open file\n");
}

✓ After

if (open("file.txt", O_RDONLY) == -1) {
    printf("Error opening file: %s\n", strerror(errno));
}

What It Enables

Using errno lets your program understand and respond to errors clearly, making your code more reliable and user-friendly.

Real Life Example

When a program tries to read a configuration file but it's missing, errno helps show a clear message like "File not found" instead of crashing silently.

Key Takeaways

Manual error checks often miss details and confuse users.

errno provides specific error info after failures.

This makes debugging and user messages much clearer.