In the past I\'ve worked with -Wall and other switches for gcc to eliminate every compiler warning for projects I\'ve been involved in. Similarly, in Perl, I always program wit
Eclipse, IntelliJ and other modern code quality systems have huge numbers of available warnings.
Cleaning up warnings is a useful practice, if for no other reason than to quiet down the noise. Your code probably already has some of these that are real bugs.
However, many of the warnings are probably bogus. Some warnings from Eclipse are things like micro-optimizations or stylistic nitpicking. This means that some of your cleanups must be tweaking the settings of your tool, rather than code changes or localized suppression directives.