The @SuppressWarnings annotation disables certain compiler warnings. In this case, the warning about deprecated code (“deprecation”) and unused local variables or unused private methods (“unused”). This article explains the possible values.
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
Yes, these can be suppressed. Normally, I’m opposed to suppressing warnings, but in this case, structs used for interop absolutely requires some fields to be present, even though you never intend to (or can) use them, so in this case I think it should be justified. Normally, to suppress those two warnings, you would fix … Read more
With the @Suppress annotation You can suppress any diagnostics on any declaration or expression. Examples: Suppress warning on parameter: fun foo(a: Int, @Suppress(“UNUSED_PARAMETER”) b: Int) = a Suppress all UNUSED_PARAMETER warnings inside declaration @Suppress(“UNUSED_PARAMETER”) fun foo(a: Int, b: Int) { fun bar(c: Int) {} } @Suppress(“UNUSED_PARAMETER”) class Baz { fun foo(a: Int, b: Int) { … Read more
Just use suppressMessages() around your library() call: edd@max:~$ R R version 2.14.1 (2011-12-22) Copyright (C) 2011 The R Foundation for Statistical Computing ISBN 3-900051-07-0 Platform: x86_64-pc-linux-gnu (64-bit) […] R> suppressMessages(library(ROCR)) R> # silently loaded R> search() [1] “.GlobalEnv” “package:ROCR” # it’s really there [3] “package:gplots” “package:KernSmooth” [5] “package:grid” “package:caTools” [7] “package:bitops” “package:gdata” [9] “package:gtools” “package:stats” … Read more
To disable warnings on a per-file basis, using Xcode 3 and llvm-gcc-4.2 you can use: #pragma GCC diagnostic ignored “-Wwarning-flag” Where warning name is some gcc warning flag. This overrides any warning flags on the command line. It doesn’t work with all warnings though. Add -fdiagnostics-show-option to your CFLAGS and you can see which flag … Read more
To avoid the warning: do not import the class instead use the fully qualified class name and use it in as few locations as possible.
You may try to include library headers using -isystem instead of -I. This will make them “system headers” and GCC won’t report warnings for them.
Use the following: @SuppressWarnings({“unused”, “unchecked”})
Found this on github… import warnings warnings.simplefilter(action=’ignore’, category=FutureWarning) import pandas