If you really, really must do this, and you are sure you are not making a mistake, check out the @SuppressWarnings annotation. I suppose in your case you need @SuppressWarnings(“fallthrough”) Is the annotation @SuppressWarnings (javadoc) what you are looking for? For example: @SuppressWarnings(“unchecked”) public void someMethod(…) { … }
For most of the suppression types, you omit the wildcard, like so: { name Memcheck:Cond obj:/path/to/lib/lib.so.10.1 } { name Memcheck:Free obj:/path/to/lib/lib.so.10.1 } { name Memcheck:Value8 obj:/path/to/lib/lib.so.10.1 } Note that you must list each type of error separately, you can’t wildcard them. You must also list the entire pathname of the library (as shown by valgrind, … Read more
No, and an enhancement request [1] for such a feature was closed as wontfix. I agree it would be useful. I expect that the Scala core team aren’t against the idea, but they have finite resources and many higher priorities. update: this feature was eventually implemented in scala 2.13.2 release on 2020-04-22, see this answer … Read more
When using GCC you can use the -isystem flag instead of the -I flag to disable warnings from that location. So if you’re currently using gcc -Iparent/path/of/bar … use gcc -isystem parent/path/of/bar … instead. Unfortunately, this isn’t a particularly fine-grained control. I’m not aware of a more targeted mechanism.
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
Starting with version 3.8 M6, Eclipse (to be exact: the JDT) has built-in functionality for this. It is configurable through a project’s build path: Project properties > Java Build Path > Compiler > Source Announced here: Eclipse 3.8 and 4.2 M6 – New and Noteworthy, called Selectively ignore errors/warnings from source folders. That’s also where … Read more
Use this method around (a) header(s) that you cannot or don’t want to change, but which you need to include. You can selectively, and temporarily disable all warnings like this: #pragma warning(push, 0) // Some include(s) with unfixable warnings #pragma warning(pop) Instead of 0 you can optionally pass in the warning number to disable, so … Read more
The interface declares the method with a raw type. In that case, you can’t override it nicely without having the warning. The origin of your problem is that the Spring interface was declared to be Java 1.4 compliant. Note that Spring 3.0 is supposed to deliver all classes as Java 1.5 compliant, so that would … Read more
Assuming you are running the memcheck tool and you want to ignore Leak errors in libcrypto only, you could put a suppression like: { ignore_libcrypto_conditional_jump_errors Memcheck:Leak … obj:*/libcrypto.so.* } … into a file and pass it to valgrind with –suppressions=*FILENAME*. To ignore Leak errors in all shared libraries under any lib directory (/lib, /lib64, /usr/lib, … Read more
You can suppress Incomplete Implementation warnings by adding #pragma clang diagnostic ignored “-Wincomplete-implementation” just above the @implementation Hope this helps EDIT After being told in the comments that this didn’t work for someone and finding out the reason was because it was a different warning they were getting I have done a bit of playing … Read more