A common idiom to use here would be for(;;) {...}
But check this out:
#define SOME_MACRO( foo, bar ) \
do \
{ \
foo(); \
bar(); \
} while (0) // warning: conditional expression
// is constant
Most insidiously, you can't wrap the macro with #pragma warning (push, disable, pop) because it's a macro. So the warning can only be suppressed where you call it, not where it's defined!
That's why I globally disable this warning in all my projects. I've never been saved by it, and it's sucked away enough of my life.
#include <stdio.h>
#define ADD(x, y, z) \
do { \
z = x + y; \
} while (0)
int main(int argc, char *argv[])
{
int z;
ADD(1, 3, z);
printf("z = %d\n", z);
return 0;
}
It was a poor design choice by Microsoft. All of their compilers emit the warning when using the highest warning level.
Thanks again --- if GCC never warns, then I feel much better about globally disabling it.
Changing main's signature to int main() eliminates all warnings at -Wextra.
I've used up enough of your time already, but if you feel like it...:
Do you know if gcc has the equivalent of #pragma warning( disable: N ) ? i.e. could you disable your argc and argv warning for just that source file, and no other?
If yes, then is there a way to "scope" that disable to be within a header file? (#pragma warning(push) and #pragma warning(pop))
#pragma GCC diagnostic ignored "-Wunused-parameter"