Could someone explain to me why? All I read is trust me, but I simply can’t just trust on something because someone said so.
I tried the approach and I can’t find any bugs appearing:
#define mymacro(a) int a ## __LINE__
mymacro(prefix) = 5;
mymacro(__LINE__) = 5;
int test = prefix__LINE__*__LINE____LINE__; // fine
So why do I need to do it like this instead (quote from the webpage):
However you need a double layer of indirection when you use ##.
Basically you need to create a special macro for “token pasting” such
as:#define NAME2(a,b) NAME2_HIDDEN(a,b) #define NAME2_HIDDEN(a,b) a ## bTrust me on this — you really need to do
this! (And please nobody write me saying it sometimes works without
the second layer of indirection. Try concatenating a symbol with
__ LINE__ and see what happens then.)
Edit: Could someone also explain why he uses NAME2_HIDDEN before it’s declared below? It seems more logical to define NAME2_HIDDEN macro before I use it. Is it some sort of trick here?
The relevant part of the C spec:
The key part that determines whether you want the double indirection or not is the second sentence and the exception in it — if the parameter is involved in a
#or##operation (such as the params inmymacroandNAME2_HIDDEN), then any other macros in the argument are NOT expanded prior to doing the#or##. If, on the other hand, there’s no#or##IMMEDIATELY in the macro body (as withNAME2), then other macros in the parameters ARE expanded.So it comes down to what you want — sometimes you want all macros expanded FIRST, and then do the
#or##(in which case you want the double layer indirection) and sometime you DO NOT want the macros expanded first (in which case you CAN’T HAVE double layer macros, you need to do it directly.)