Author: Dieter Buerssner
Date: 12:19:27 07/02/03
Go up one level in this thread
On July 02, 2003 at 15:07:05, Gerd Isenberg wrote:
> Use max warning level, try intel c++.
Gerd, I found max warning level of MSVC rather annoying. It will warn about
secure macros with
#define foo() \
do { \
/* code */ \
} while (0)
while it won't warn about the more fragile usage without the do while trick. I
will get hundreds of warnings. I saw other cases, for example, where I
deliberately use unsigned int overflow. Sure, I could disable specific warnings,
but the effort seems just too much. OTOH, I find gcc with max warning level
useful. But at times, I add stupid code to my source, just because of warnings.
"Var foo might be used uninitialized". Not true, the compiler just did not see
it. I add foo=0; /* to avoid compiler warning */. Something like this migth
avoid better optimization of a future version of the compiler.
Cheers,
Dieter
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.