Fundamentals of C/C++ Macros

Macros in C/C++ provide a mechanism for compile-time symbol replacement. A common example is defining a constant like PI:

#define PI 3.14159265

This allows using PI throughout the code instead of the literal value. Macros can significant reduce code duplication when dealing with repetitive patterns.

Basic Macro Syntax

Macros are defined using #define:

#define MAX_VALUE 100
#define NULL_PTR ((void*)0)
#define API_EXPORT

During compilation, the preprocessor replcaes all instances of the macro with its definition. For example:

double circumference = diameter * PI;

Becomes:

double circumference = diameter * 3.14159265;

Parameterized Macros

Macros can accept parameters similar to functions:

#define SQUARE(x) ((x) * (x))
int result = SQUARE(5);  // Expands to ((5) * (5))

Key differences from functions:

• No type checking
• No runtime overhead
• Not debuggable
• Cannot be recursive

Common Pitfalls

1. Operator Precedence Issues:

#define MULTIPLY(a, b) a * b
int val = MULTIPLY(2+3, 4);  // Expands to 2+3*4 = 14

Solution: Always parenthesize parameters:

#define MULTIPLY(a, b) ((a) * (b))

2. Multi-line Macros:

#define PROCESS(x) \
    do { \
        int temp = (x); \
        temp *= 2; \
        return temp; \
    } while(0)

3. String Conversion (#):

#define STR(x) #x
const char* s = STR(test);  // "test"

4. Token Pasting (##):

#define VAR(name) var_##name
int VAR(count);  // int var_count;

Advanced Techniques

1. Variadic Macros:

#define LOG(fmt, ...) printf(fmt, ##__VA_ARGS__)
LOG("Value: %d", 42);

2. Debugging Macros:

#define DEBUG_PRINT(x) \
    do { \
        printf("%s = %d\n", #x, (x)); \
    } while(0)

3. Header Guards:

#ifndef MY_HEADER_H
#define MY_HEADER_H
// Header content
#endif

4. Platform-Specific Code:

#ifdef _WIN32
    // Windows-specific code
#else
    // Other platform code
#endif

Best Practices

1. Always parenthesize macro parameters and entire expressions
2. Use do { } while(0) for multi-statement macros
3. Choose unique macro names to avoid collisions
4. Consider using inline functions instead of complex macros
5. Document macro behavior clearly