compiler-warnings

I would like to get rid of the warnings. When I compile the source code with gcc -Wall -ansi -o test test.c I get back test.c: In function ‘main’: test.c:12: warning: implicit declaration of function ‘getresuid’ test.c:14: warning: implicit declaration of function ‘seteuid’ When I compile it without -ansi switch gcc -Wall -o test test.c I see on the terminal test.c: In function ‘main’: test.c:12: warning: implicit declaration of function ‘getresuid’ I would like to use -ansi switch and get rid of warnings. How can I achieve my goal ? /* this is the test.c */ #include <stdio.h> #include <sys

Even warning level 4 and "all warnings" does not make the 6000 series warnings appear. Actually enabling these "Code Analysis" warnings has it's own dialog. In your project properties, you must check "Enable Code Analysis on Build" to make it work. This code should then show error 6246: #include <stdio.h> int main() { int x ; { int x = 6 ; printf( "%d\n", x ) ; } } warning C6246: Local declaration of 'x' hides declaration of the same name in outer scope. This setting appears to be completely independent of the "Configuration Properties/C/C++/General/Warning Level" setting in the properties

-Wshadow will "Warn whenever a local variable shadows another local variable.". Is there an equivalent in Visual C++ (2008)? I tried /W4 but it didn't pick up on it. I also tried Cppcheck but that didn't see it either. e.g. if I inadvertently do: class A { private: int memberVar; public: void fn() { int memberVar = 27; } }; I would really like to know about it! I am afraid no. You could perhaps try compiling your code with Clang: it has this warning (and a lot of others) it has a compatibility mode for MSVC headers (and can build most of MFC) We use gcc at work, to build our code, but compile

I'm sick to death of Xcode's prolific use of live "unused variable" warnings while I am typing. I keep thinking I have an error in my syntax, stop what I'm doing, check the warning, only to see it's an unused variable warning. Of course it's unused, I just typed it! I don't mind the compile-time unused variable warnings, those are very useful, but I hate the live warnings as I'm typing code. Is there any way I can turn off this warning completely everywhere, either app-wide or for an entire project? dfri It seems as of currently, we cannot suppress specific warnings in the way #pragma clang

I'm using Keil uVision v4.74 and have enabled the option "All Warnings". I wrote the following intentional code: if(condition matched) { //do something } When I rebuilt my project, I got 0 errors, 0 warnings. However, when I accidentally wrote: if(condition matched); { //do something } I also got 0 errors, 0 warnings. It was next to impossible for me to find out that a small ; following the if condition was the root of the problem. Why didn't the compiler treat it as a warning and inform me? It's not an error because an empty statement is a valid statement; however, since it's certainly

Is there a way to suppress warnings in C# similar to Java's @SuppressWarnings annotation? Failing that, is there another way to suppress warnings in Visual Studio? Yes. For disabling, use : #pragma warning disable 0169, 0414, anyothernumber Where the numbers are the identifiers of the warnings that you can read from compiler output. To reenable the warnings after a particular part of code (which is a good idea) use: #pragma warning restore 0169, anythingelse This way you can make the compiler output clean, and keep yourself safe because the warnings will only be suppressed for that particular

Compare this method: void doStuff(String val) { if (val == null) { val = DEFAULT_VALUE; } // lots of complex processing on val } ... to this method: void doStuff(String origVal) { String val = origVal; if (val == null) { val = DEFAULT_VALUE; } // lots of complex processing on val } For the former method, Eclipse emits the warning "The parameter 'val' should not be assigned". Why? To my eye, the former is cleaner. For one thing, it doesn't force me to come up with two good names for val (coming up with one good one is hard enough). (Note: Assume there is no field named val in the enclosing

I know unsigned int can't hold negative values. But the following code compiles without any errors/warnings. unsigned int a = -10; When I print the variable a , I get a wrong value printed. If unsigned variables can't hold signed values, why do compilers allow them to compile without giving any error/warning? Any thoughts? Edit Compiler : VC++ compiler Solution Need to use the warning level 4. Microsoft Visual C++: warning C4245: 'initializing' : conversion from 'int' to 'unsigned int', signed/unsigned mismatch On warning level 4. G++ Gives me the warning: warning: converting of negative value