Replacing text macros

 

C

Language

Headers

Type support

Program utilities

Variadic function support

Error handling

Dynamic memory management

Date and time utilities

Strings library

Algorithms

Numerics

Input/output support

Localization support

Atomic operations (C11)

Thread support (C11)

Technical Specifications

 

C language

ASCII chart

Basic concepts

Keywords

Preprocessor

Statements

Expressions

Initialization

Declarations

Functions

Miscellaneous

history of C

Technical Specifications

 

Preprocessor

#if#ifdef#ifndef#else#elif#endif

#define#undef#,## operators

#include

#error

#pragma

#line

 

The preprocessor supports text macro replacement and function-like text macro replacement.

Syntax

#define identifier replacement-list(optional)	(1)
#define identifier( parameters ) replacement-list	(2)
#define identifier( parameters, ... ) replacement-list	(3)	(since C99)
#define identifier( ... ) replacement-list	(4)	(since C99)
#undef identifier	(5)

Explanation

#define directives

The #define directives define the identifier as a macro, that is they instruct the compiler to replace all successive occurrences of identifier with replacement-list, which can be optionally additionally processed. If the identifier is already defined as any type of macro, the program is ill-formed unless the definitions are identical.

Object-like macros

Object-like macros replace every occurrence of a defined identifier with replacement-list. Version (1) of the #define directive behaves exactly like that.

Function-like macros

Function-like macros replace each occurrence of a defined identifier with replacement-list, additionally taking a number of arguments, which then replace corresponding occurrences of any of the parameters in the replacement-list.

The syntax of a function-like macro invocation is similar to the syntax of a function call: each instance of the macro name followed by a ( as the next preprocessing token introduces the sequence of tokens that is replaced by the replacement-list. The sequence is terminated by the matching ) token, skipping intervening matched pairs of left and right parentheses.

The number of arguments must be the same as the number of arguments in the macro definition (parameters) or the program is ill-formed. If the identifier is not in functional-notation, i.e. does not have parentheses after itself, it is not replaced at all.

Version (2) of the #define directive defines a simple function-like macro.

Version (3) of the #define directive defines a function-like macro with variable number of arguments. The additional arguments can be accessed using __VA_ARGS__ identifier, which is then replaced with arguments, supplied with the identifier to be replaced.

Version (4) of the #define directive defines a function-like macro with variable number of arguments, but no regular arguments. The arguments can be accessed only with __VA_ARGS__ identifier, which is then replaced with arguments, supplied with identifier to be replaced.

Note: if an argument of a function-like macro includes commas that are not protected by matched pairs of left and right parentheses (such as macro(array[x = y, x + 1]) or atomic_store (p, (struct S){ a, b });), the comma is interpreted as macro argument separator, causing a compilation failure due to argument count mismatch.

# and ## operators

In function-like macros, a # operator before an identifier in the replacement-list runs the identifier through parameter replacement and encloses the result in quotes, effectively creating a string literal. In addition, the preprocessor adds backslashes to escape the quotes surrounding embedded string literals, if any, and doubles the backslashes within the string as necessary. All leading and trailing whitespace is removed, and any sequence of whitespace in the middle of the text (but not inside embedded string literals) is collapsed to a single space. This operation is called "stringification". If the result of stringification is not a valid string literal, the behavior is undefined.

When # appears before __VA_ARGS__, the entire expanded __VA_ARGS__ is enclosed in quotes: #define showlist(...) puts(#__VA_ARGS__) showlist(); // expands to puts("") showlist(1, "x", int); // expands to puts("1, \"x\", int")

(since C99)

A ## operator between any two successive identifiers in the replacement-list runs parameter replacement on the two identifiers and then concatenates the result. This operation is called "concatenation" or "token pasting". Only tokens that form a valid token together may be pasted: identifiers that form a longer identifier, digits that form a number, or operators + and = that form a +=. A comment cannot be created by pasting / and * because comments are removed from text before macro substitution is considered. If the result of concatenation is not a valid token, the behavior is undefined.

Note: Some compilers offer an extension that allows ## to appear after a comma and before __VA_ARGS__, in which case the ## does nothing when __VA_ARGS__ is non-empty, but removes the comma when __VA_ARGS__ is empty: this makes it possible to define macros such as fprintf (stderr, format, ##__VA_ARGS__).

The order of evaluation of # and ## operators is unspecified.

#undef directive

The #undef directive undefines the identifier, that is it cancels the previous definition of the identifier by #define directive. If the identifier does not have an associated macro, the directive is ignored.

Predefined macros

The following macro names are predefined in any translation unit:

__STDC__	expands to the integer constant 1. This macro is intended to indicate a conforming implementation (macro constant)
__STDC_VERSION__ (C95)	expands to an integer constant of type long whose value increases with each version of the C standard: 199409L (C95) 199901L (C99) 201112L (C11) 201710L (C17) (macro constant)
__STDC_HOSTED__ (C99)	expands to the integer constant 1 if the implementation is hosted (runs under an OS), ​0​ if freestanding (runs without an OS) (macro constant)
__FILE__	expands to the name of the current file, as a character string literal, can be changed by the #line directive (macro constant)
__LINE__	expands to the source file line number, an integer constant, can be changed by the #line directive (macro constant)
__DATE__	expands to the date of translation, a character string literal of the form "Mmm dd yyyy". The name of the month is as if generated by asctime and the first character of "dd" is a space if the day of the month is less than 10 (macro constant)
__TIME__	expands to the time of translation, a character string literal of the form "hh:mm:ss", as in the time generated by asctime() (macro constant)

The following additional macro names may be predefined by an implementation:

__STDC_ISO_10646__ (C99)	expands to an integer constant of the form yyyymmL, if wchar_t uses Unicode; the date indicates the latest revision of Unicode supported (macro constant)
__STDC_IEC_559__ (C99)	expands to 1 if IEC 60559 is supported (macro constant)
__STDC_IEC_559_COMPLEX__ (C99)	expands to 1 if IEC 60559 complex arithmetic is supported (macro constant)
__STDC_UTF_16__ (C11)	expands to 1 if char16_t use UTF-16 encoding (macro constant)
__STDC_UTF_32__ (C11)	expands to 1 if char32_t use UTF-32 encoding (macro constant)
__STDC_MB_MIGHT_NEQ_WC__ (C99)	expands to 1 if 'x' == L'x' might be false for a member of the basic character set, such as on EBCDIC-based systems that use Unicode for wchar_t (macro constant)
__STDC_ANALYZABLE__ (C11)	expands to 1 if analyzability is supported (macro constant)
__STDC_LIB_EXT1__ (C11)	expands to an integer constant 201112L if bounds-checking interfaces are supported (macro constant)
__STDC_NO_ATOMICS__ (C11)	expands to 1 if atomic types and atomic operations library are not supported (macro constant)
__STDC_NO_COMPLEX__ (C11)	expands to 1 if complex types and complex math library are not supported (macro constant)
__STDC_NO_THREADS__ (C11)	expands to 1 if multithreading is not supported (macro constant)
__STDC_NO_VLA__ (C11)	expands to 1 if variable-length arrays are not supported (macro constant)

The values of these macros (except for __FILE__ and __LINE__) remain constant throughout the translation unit. Attempts to redefine or undefine these macros result in undefined behavior.

The predefined variable __func__ (see function definition for details) is not a preprocessor macro, even though it is sometimes used together with __FILE__ and __LINE__, e.g. by assert.

(since C99)

Example

Run this code

#include <stdio.h>
 
//make function factory and use it
#define FUNCTION(name, a) int fun_##name(int x) { return (a)*x;}
 
FUNCTION(quadruple, 4)
FUNCTION(double, 2)
 
#undef FUNCTION
#define FUNCTION 34
#define OUTPUT(a) puts( #a )
 
int main(void)
{
    printf("quadruple(13): %d\n", fun_quadruple(13) );
    printf("double(21): %d\n", fun_double(21) );
    printf("%d\n", FUNCTION);
    OUTPUT(million);               //note the lack of quotes
}

Output:

quadruple(13): 52
double(21): 42
34
million

References

• C11 standard (ISO/IEC 9899:2011):

• 6.10.3 Macro replacement (p: 166-173)

• 6.10.8 Predefined macro names (p: 175-176)

• C99 standard (ISO/IEC 9899:1999):

• 6.10.3 Macro replacement (p: 151-158)

• 6.10.8 Predefined macro names (p: 160-161)

• C89/C90 standard (ISO/IEC 9899:1990):

• 3.8.3 Macro replacement

• 3.8.8 Predefined macro names

See also

C++ documentation for Replacing text macros