constant value saving expression
in , mentioned move for(;;) impression since while(true) impression gives warning messages msvc saving countenance being constant.
this bewildered me greatly, given consistent values saving expressions useful proceed avoiding #ifdef hell. instance, have your header:
#ifdef config_foo
extern int foo_enabled;
#else
#define foo_enabled 0
#endif
and formula simply saving trust compiler undervalue passed formula config_foo isn't defined:
if (foo_enabled) {
...
}
instead carrying exam config_foo each foo_enabled used:
#ifdef config_foo
if (foo_enabled) {
...
}
#endif
this settlement pattern used linux heart (for instance, include/linux/cpumask.h defines several macros 1 0 smp noxious duty smp enabled).
what reason msvc warning? additionally, there improved proceed prevaricate #ifdef harm but carrying invalidate warning? an overly extended warning should enabled general?
Comments
Post a Comment