From what I can tell in the docs, you can’t do it on the command-line. According to the javac documentation, -Xlint:none only disables warnings “not mandated by the Java Language Specification”. It appears that warning you of the use of deprecated APIs is managed by the language spec. Your best option would be to fix … Read more
I inherited a project that contained a lot of 320 code, and that code base threw several warnings and static analyzer errors at me that I had no interest in fixing since I will be removing that code from the project in the near future. You can disable static analyzer warnings for a specific file … Read more
The reason is because they’re initialized in the order they’re declared in your class, not the order you initialize them in the constructor and it’s warning you that your constructor’s order won’t be used. This is to help prevent errors where the initialization of b depends on a or vice-versa. The reason for this ordering … Read more
Using Xcode 4.3.2 and found out that this seems to work (less writing) BOOL saved __unused;
It is clearly a compiler bug, and it was introduced in C# 3.0 — right around the time that I heavily refactored the reachability checker. This is probably my bad, sorry. The bug is completely benign; basically, we just forgot a case in the warning reporter. We generate the reachability information correctly; as others have … Read more
Ensure the files are under the gen folder, the typical home for all generated .java files. Then in the project properties, under Java Build Path, set Ignore optional compile problems for that folder to Yes. If your project structure requires your files be in a folder other than gen, add that folder to the Java … Read more
-Wmissing-braces will no longer be enabled in GCC’s -Wall (for C++ mode), as of 4.8, for precisely the reason you describe. For current versions of GCC, either disable or ignore the warning, the code you have is written the way it should be. The warning is probably meant to cover code such as struct A … Read more
If your third-party libraries are added as a separate target, you can check Inhibit all warnings for that specific target to turn all warnings off. If your library is added as plain source files to your current target, you can set -w compiler flag for individual sources to mute all warnings in them. You have … Read more
If you need an option which works on both gcc and clang, your best bet is probably -Wmissing-prototypes. As indicated in the gcc documentation, this will trigger if a global function is defined and either: There was no previous declaration; or The previous declaration had no prototype. It does not complain if the previous declaration … Read more
It is nothing to worry about. In the last few releases of MSVC, they’ve gone into full security-paranoia mode. std::copy issues this warning when it is used with raw pointers, because when used incorrectly, it can result in buffer overflows. Their iterator implementation performs bounds checking to ensure this doesn’t happen, at a significant performance … Read more