Can macros be overloaded by number of arguments?

by

(Edit: See the end for a ready-made solution.)

To get an overloaded macro, first we need a macro which selects between several implementations. This part doesn’t use a variadic macro. Then a variadic macro which generically counts its arguments produces a selector. Plugging the argument count into a dispatcher produces an overloaded macro.

Caveat: This system cannot tell the difference between zero and one arguments because there is no difference between no argument, and a single empty argument. They both look like MACRO().

To select between implementations, use the macro catenation operator with a series of function-like macros.

#define select( selector, ... ) impl ## _ ## selector( __VA_ARGS__ )
#define impl_1() meh
#define impl_2( abc, xyz ) # abc "wizza" xyz()
//etc

// usage: select( 1 ) => impl_1() => meh
//        select( 2, huz, bar ) => impl_2( huzza, bar ) => "huz" "wizza" bar()

Because the ## operator suppresses macro expansion of its arguments, it’s better to wrap it in another macro.

#define CAT( A, B ) A ## B
#define SELECT( NAME, NUM ) CAT( NAME ## _, NUM )

To count arguments, use __VA_ARGS__ to shift arguments like so (this is the clever part):

#define GET_COUNT( _1, _2, _3, _4, _5, _6 /* ad nauseam */, COUNT, ... ) COUNT
#define VA_SIZE( ... ) GET_COUNT( __VA_ARGS__, 6, 5, 4, 3, 2, 1 )

Library code:

#define CAT( A, B ) A ## B
#define SELECT( NAME, NUM ) CAT( NAME ## _, NUM )

#define GET_COUNT( _1, _2, _3, _4, _5, _6 /* ad nauseam */, COUNT, ... ) COUNT
#define VA_SIZE( ... ) GET_COUNT( __VA_ARGS__, 6, 5, 4, 3, 2, 1 )

#define VA_SELECT( NAME, ... ) SELECT( NAME, VA_SIZE(__VA_ARGS__) )(__VA_ARGS__)

Usage:

#define MY_OVERLOADED( ... ) VA_SELECT( MY_OVERLOADED, __VA_ARGS__ )
#define MY_OVERLOADED_1( X ) foo< X >
#define MY_OVERLOADED_2( X, Y ) bar< X >( Y )
#define MY_OVERLOADED_3( X, Y, Z ) bang_ ## X< Y >.Z()

More Related Contents:

  1. C++ preprocessor __VA_ARGS__ number of arguments
  2. MSVC++ variadic macro expansion
  3. Are Variadic macros nonstandard?
  4. Why are preprocessor macros evil and what are the alternatives?
  5. How do I see a C/C++ source file after preprocessing in Visual Studio?
  6. How to detect reliably Mac OS X, iOS, Linux, Windows in C preprocessor? [duplicate]
  7. Stringification – how does it work?
  8. Combining C++ and C – how does #ifdef __cplusplus work?
  9. Define preprocessor macro through CMake?
  10. C++ preprocessor #define-ing a keyword. Is it standards conforming?
  11. Overload resolution between object, rvalue reference, const reference
  12. Can we overload operators for built-in types like int or float?
  13. Any reason to overload global new and delete?
  14. Namespaces in C
  15. Representing big numbers in source code for readability?
  16. Why does the most negative int value cause an error about ambiguous function overloads?
  17. Inheritance and method overloading
  18. Why is it not possible to overload class templates?
  19. What’s the difference between the WIN32 and _WIN32 defines in C++
  20. Somehow register my classes in a list
  21. Most terse and reusable way of wrapping template or overloaded functions in function objects
  22. Can I redefine a C++ macro then define it back?
  23. Is the backslash acceptable in C and C++ #include directives?
  24. “No newline at end of file” compiler warning
  25. overloaded functions are hidden in derived class
  26. How to test if preprocessor symbol is #define’d but has no value?
  27. How does C++ Preprocessors work?
  28. What is the NDEBUG preprocessor macro used for (on different platforms)?
  29. STL algorithms: Why no additional interface for containers (additional to iterator pairs)?
  30. C preprocessor macro specialisation based on an argument

Leave a Comment