#undef in C: What It Does and How to Use It

#undef in C is a preprocessor directive used to remove or cancel a previously defined macro. It tells the compiler to forget the macro name and its replacement, so it no longer applies in the code after #undef.

How It Works

The #undef directive works like erasing a label you put on a box. Imagine you labeled a box "FRAGILE" to remind yourself to handle it carefully. Later, if you remove that label, the box is treated like any other. Similarly, when you define a macro with #define, you give a name a special meaning or value. Using #undef removes that meaning.

This is useful because the C preprocessor replaces all occurrences of the macro name with its value before the program is compiled. If you want to stop this replacement for some reason, #undef tells the preprocessor to forget the macro from that point onward.

Example

This example shows how #undef removes a macro definition so it no longer affects the code.

c

#include <stdio.h>

#define PI 3.14

int main() {
    printf("PI before undef: %f\n", PI);

    #undef PI

    // After undef, PI is no longer defined, so this will cause an error if uncommented
    // printf("PI after undef: %f\n", PI);

    printf("PI is undefined now, so no replacement happens here.\n");
    return 0;
}

Output

PI before undef: 3.140000
PI is undefined now, so no replacement happens here.

When to Use

You use #undef when you want to remove a macro definition to avoid conflicts or change behavior in different parts of your program. For example:

• If you include multiple header files that define the same macro differently, you can #undef one before redefining it.
• When debugging, you might want to disable a macro temporarily without removing the original #define line.
• In conditional compilation, you can #undef a macro to switch between different code paths.

Key Points

• #undef removes a macro definition from the preprocessor.
• It affects code only after the #undef line.
• Using #undef helps avoid macro name conflicts.
• It does not delete variables or functions, only macro names.

Key Takeaways

#undef cancels a macro so it no longer replaces text in code.

Use #undef to avoid conflicts or change macro behavior mid-file.

#undef only affects macros, not variables or functions.

Macros removed by #undef must be redefined if needed again.

It helps keep your code flexible and easier to manage when using macros.