Variadic macro
From Wikipedia, the free encyclopedia
 |
The introduction to this article provides insufficient context for those unfamiliar with the subject. Please help improve the article with a good introductory style. |
A variadic macro is a feature of the C preprocessor whereby a macro may be declared to accept a varying number of arguments.
Variable-argument macros were introduced in the ISO/IEC 9899:1999 (C99) revision of the C Programming Language standard in 1999. They are currently not part of the C++ programming language, though many popular C++ implementations support variable-argument macros as an extension, and it is expected that variadic macros may be added to C++ at a later date.
Contents |
[edit] Declaration syntax
The declaration syntax is similar to that of variadic functions: an ellipsis "..." is used to indicate that one or more (possibly empty) arguments must be passed. During macro expansion each occurrence of the special identifier __VA_ARGS__ in the macro replacement list is replaced by the passed arguments.
No means is provided to access individual arguments in the variable argument list, nor to find out how many were passed.
[edit] Support
The GNU Compiler Collection, since 3.0, C++Builder 2006 and Visual Studio 2005 [1] support variable-argument macros, both when compiling C and C++ code. In addition, GCC supports variadic macros when compiling Objective C.
[edit] Example
If a printf-like function dprintf() were desired, which would take the file and line number from which it was called as arguments, the following macro might be used:
void realdprintf (char const *file, int line, char const *fmt, ...); #define dprintf(...) realdprintf(__FILE__, __LINE__, __VA_ARGS__)
dprintf() could then be called as:
dprintf("Hello, world");
which expands to:
realdprintf(__FILE__, __LINE__, "Hello, world");
or:
dprintf("%d + %d = %d", 2, 2, 5);
which expands to:
realdprintf(__FILE__, __LINE__, "%d + %d = %d", 2, 2, 5);
Without variadic macros, writing wrappers to printf is not directly possible. The standard workaround is to use the stdargs functionality of C/C++, and have the function call vprintf instead.
