Avoiding unused variables warnings when using assert() in a Release build

Question

Sometimes a local variable is used for the sole purpose of checking it in an assert(), like so -

int Result = Func();
assert( Result == 1 );

<

Answer 1

Certainly you use a macro to control your assert definition, such as "_ASSERT". So, you can do this:

#ifdef _ASSERT 
int Result =
#endif /*_ASSERT */
Func();
assert(Result == 1);