Nested macros

[The D0ct0r]

Hey,

please consider the following:

#if DEBUG
#define SOMEMACRO(type, name, value) (type) (name) = (value)
#else
#define SOMEMACRO(type, name, value) #define (name) (value)
#endif

If I define DEBUGging, i want the variable (name) to be a variable, but
if not, I want it to be a constant. When I compile this, the preprocessor
starts complaining at the fourth line, because of the second #define. Is
this OT here? And if not, how should I solve this?

the d0ct0r

[gnuyuva]

On May 15, 11:21 am, The D0ct0r <[e-mail]:

Hey,

please consider the following:

#if DEBUG
#define SOMEMACRO(type, name, value) (type) (name) = (value)
#else
#define SOMEMACRO(type, name, value) #define (name) (value)

Why don't you define this macro like this:
#define SOMEMACRO(type, name, value) static const type name = value;

With such constructs, you can construct complex types also, not only
PODs.

#endif

If I define DEBUGging, i want the variable (name) to be a variable, but
if not, I want it to be a constant. When I compile this, the preprocessor
starts complaining at the fourth line, because of the second #define. Is
this OT here? And if not, how should I solve this?

the d0ct0r

[James Kanze]

On May 15, 8:21 am, The D0ct0r <[e-mail]:

please consider the following:

#if DEBUG
#define SOMEMACRO(type, name, value) (type) (name) = (value)
#else
#define SOMEMACRO(type, name, value) #define (name) (value)
#endif

If I define DEBUGging, i want the variable (name) to be a
variable, but if not, I want it to be a constant. When I
compile this, the preprocessor starts complaining at the
fourth line, because of the second #define.

The results of macro expansion are not processed as
pre-processing declarations, even if they look like one.

Is this OT here?

No.

And if not, how should I solve this?

You can't use a macro to generate a #define. On the other hand,
you don't want to use #define for constants in C++ anyway.
Something like:

#if DEBUG
#define SOMEMACRO( type, name, value ) type name = value
#else
#define SOMEMACRO( type, name, value ) type const name value
#endif

would probably work. (Note that you cannot put parentheses
around the type. A declaration like:
(int) (toto) = (10) ;
is not legal. You might also want to make the variables
static.)

Also, I very seriously question the wisdom of this. If there's
any reason for the values to not be const, don't make them
const. And if there's not, they should be const in the debug
build as well.

--
James Kanze (GABI Software) email:ja*********@gmail.com
Conseils en informatique orientée objet/
Beratung in objektorientierter Datenverarbeitung
9 place Sémard, 78210 St.-Cyr-l'École, France, [phone]