rtel wrote on Friday, March 30, 2007:
Compiling the same code base with many different compilers is a pain. Code you add to prevent a warning on one compiler will cause a warning on another. Things such as using qualifiers on pointers [( volatile char * ) for example] will cause warnings that the qualifier has no meaning on some, while others will complain that the qualifier is missing if you leave it off.
In this case the usual method to prevent a warning is to (void) it, as when getting rid of the Lint warning that a function return type is ignored.
Setting the value to itself could perceivably cause a warning on some compilers (I have not tried it will all of them) that the line has no effect.
Can you selectively prevent the warning from being issued in the project configuration?