RSS

Supported Values for @SuppressWarnings

Fri, Oct 5, 2007    (Rating: 4.43 stars, Click to rate this article!) Loading ... Loading ...

Technology


If you are a Java developer and use the new @SuppressWarnings annotation in your code from time-to-time to suppress compiler warnings you, like me, have wondered probably about a million times already just exactly what are the supported values that can be used with this annotation.

The reason the list isn’t easy to find is because it’s compiler specific, which means Sun may have a different set of supported values than say IBM, GCJ or Apache Harmony.

Fortunately for us, the Eclipse folks have documented the values they support (As of Eclipse 3.3), here they are for reference:

  • all to suppress all warnings
  • boxing to suppress warnings relative to boxing/unboxing operations
  • cast to suppress warnings relative to cast operations
  • dep-ann to suppress warnings relative to deprecated annotation
  • deprecation to suppress warnings relative to deprecation
  • fallthrough to suppress warnings relative to missing breaks in switch statements
  • finally to suppress warnings relative to finally block that don’t return
  • hiding to suppress warnings relative to locals that hide variable
  • incomplete-switch to suppress warnings relative to missing entries in a switch statement (enum case)
  • nls to suppress warnings relative to non-nls string literals
  • null to suppress warnings relative to null analysis
  • restriction to suppress warnings relative to usage of discouraged or forbidden references
  • serial to suppress warnings relative to missing serialVersionUID field for a serializable class
  • static-access to suppress warnings relative to incorrect static access
  • synthetic-access to suppress warnings relative to unoptimized access from inner classes
  • unchecked to suppress warnings relative to unchecked operations
  • unqualified-field-access to suppress warnings relative to field access unqualified
  • unused to suppress warnings relative to unused code

TIP: For the folks that haven’t used @SuppressWarnings before, the syntax looks like this:

@SuppressWarnings(”unused”)

and can be placed above almost any piece of code that is causing a compiler warning to popup for your class.

Share This on Your Favorite Social Network:
  • Digg
  • del.icio.us
  • Facebook
  • Mixx
  • Google
  • Fark
  • Furl
  • Propeller
  • Reddit
  • Technorati
  • StumbleUpon
  • description
  • MisterWong
  • TwitThis
  • Slashdot
  • SphereIt
, ,

This post was written by:

Editor - who has written 1535 posts on The “Break it Down” Blog.

Bringing you summarized technical news, announcement and reviews quickly and to the point.

10 Comments For This Post

  1. ken krueger Says:

    Thanks! Been lookin’ for that!

  2. Riyad Kalla Says:

    No problem, glad it helped!

    I couldn’t believe how hard it was to find a list when I originally went looking, so I knew I had to blog it ;)

  3. rakesh Says:

    Wow, thats super cool :)

  4. Anonymous Says:

    cool. thanx a bunch to folks who got this online

  5. BlaqPoet Says:

    Thanks for this list :)

  6. Editor Says:

    No problem, glad it could help! (I know that I just keep this page bookmarked any time I’m coding now, they really should just add this to the auto-complete list in the editor IMO… or some agreed up on sub-set between Eclipse JDT/Sun Javac or something…)

  7. Alex Says:

    Wow - thx: likewise, can’t believe how hard this is to find …

  8. Paulo Says:

    Big Thanks for the list! looked and found your blog ;)

  9. Editor Says:

    Paulo, glad it helped!

  10. Mike Nelson Says:

    Rock. Thanks!

Leave a Reply