I prefer them to be errors. Warnings are too easy to ignore, even when
there are only a few of them...
Paul Ferraro wrote:
But they are not errors... I'd rather be able to easily identify
compilation errors than identify warnings.
e.g. I had to revert the compiler warning settings so that I could track
down the uncompilable AbstractFormComponent in CVS head.
If you are having an issue with too many warnings, then wouldn't it be
better to change the compiler settings to "ignore" the warnings you want
to ignore (e.g. warnings regarding generics), and revert these settings
back to "warning"?
Howard Lewis Ship wrote:
Because those are errors? Normally, I'd want them to be warnings and
we could get rid of those warnings, but with JDK 1.5 and all the
deprecation going on, warnings are no longer useful ... lost in a sea
of useless information about generics and such.
On 8/23/05, Paul Ferraro <[EMAIL PROTECTED]> wrote:
Is there a reason why the org.eclipse.jdt.core.prefs file in CVS is set
to flag certain "unused code" warnings (e.g. unused imports,
unreferenced local variables, etc.) as errors?
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
