Preprocessor Macros & Storage Classes

In Plain English

The C preprocessor expands macros (#define) and includes headers before compilation. Storage classes dictate variable lifetime and visibility: static preserves state across function calls and limits file visibility, while extern shares global symbols across translation units.

The Mental Model

"A static local variable is a tally counter on a kitchen fridge: every time someone enters the room and clicks it, the number keeps going up and never resets to 0."

Deep Dive: How It Works

Parameterized Macros: Literal textual replacement; always parenthesize parameters (((a) > (b)) ? (a) : (b)).

Header Guards: #ifndef / #define / #endif prevents duplicate type definitions in multiple inclusions.

static Lifetime: Keeps local variable state alive across repeated function invocations.

Syntax Blueprint

#define MAX(a, b) (((a) > (b)) ? (a) : (b))

void count(void) {
    static int n = 0;
    n++;
}

Define safe parameterized macro and static variable that persists across calls.

Core Rules to Remember

Macro Parentheses: Always wrap macro arguments in parentheses to prevent operator precedence bugs.

static Variable Persistence: Allocated in the data segment once; retains value throughout process lifetime.

Header Guard Best Practice: Standard guard pattern ensures headers can be safely included in any order.

Common Beginner Traps & How to Fix Them

Mistake:Macro side effects: #define SQR(x) ((x) * (x)) called with SQR(i++).

Why it happens: i++ is expanded twice, causing unintended double increments.

How to fix: Avoid passing expressions with side effects (like i++) into preprocessor macros.

Pro Tip: Use static on helper functions in .c files to keep them private and allow the compiler to inline them aggressively.

Live Interactive Example

Hit Run Code to see it live

Static Persistence and Macros

C11 / GCC 9.2

Output Console

Click "Run Code" to view the rendered output.

How it works: static callCount persists between trackCounter calls, incrementing from 1 to 2.

Your Turn: Micro Challenge

No pressure! Edit the starter code below and test your solution with instant feedback.

Micro Exercise

Demonstrate Third Static Call

Invoke trackCounter() a 3rd time to demonstrate static variable persistence.

Sandbox Output

Click "Run & Check" to test your solution.

Finished reading and practicing?

Mark this lesson as completed to update your course progress.

Core Rules to Remember

Macro Parentheses: Always wrap macro arguments in parentheses to prevent operator precedence bugs.

static Variable Persistence: Allocated in the data segment once; retains value throughout process lifetime.

Header Guard Best Practice: Standard guard pattern ensures headers can be safely included in any order.