But if -sadly- you must use C, metaprogramming using macros is not a terrible thing.
It is a terrible thing. It's possible to do without them, and you'll like your code better. Your symbolic debugger and syntax directed editor will work properly. The poor schlub who has to fix the bugs in your code after you leave will be grateful. Your spouse will be happy and your children will prosper.
For example,
#define foo(x) ((x) + 1)
int foo(int x) { return x + 1; }
#define FOO 3
enum { FOO = 3 };
const int FOO = 3;
#if FOO == 3
bar();
#endif
if (FOO == 3) bar();
According to this stance, any code that's suppressed by the C preprocessor should either be written in an if {} statement so that it will at least continue to compile as the surrounding code changes, or be replaced with comments describing what it does (or did), if it's important enough to keep track of.
Can't really think of many good counterarguments to this. Machine dependence might be one, but then you could argue that the preprocessor is being used to cover up for an inadequate HAL.
Conditional compilation is an optimization, not a semantic intent.
> non-optimized debug builds are affected
The code size will be larger. Doesn't matter.
The optimizer will delete bar() if FOO is a manifest constant that is not 3.
extern void bar();