On 08/29/2013 04:19 PM, Eike Stepper wrote:
I'd better disable a compiler check (or findbugs rule, for that
matter) than risk that any new potential problem gets overlooked in a
sea of warnings that nobody ever wants to address. Once you've got
more than 5 warnings in the problems view, you'll never ever look at
that view again.
That makes a difference. I fundamentally believe in the concept of
technical debt (like some people do believe in God). So I think all the
contrary: most warnings are useful and meaningful and resolving them
improve code quality. They should never get ignored or hidden, even if
no-one wants to work on them, developers have to know where the quality
of their code is not optimal.
If you don't pay for your bugs/warnings now, you'll pay more later.
But this doesn't imply that we should avoid creation of new warnings
when they produce value. IMO Generics on viewers do provide value, and
are worth showing warning on legacy code. Let's look at the future, not
at the legacy ;)
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
