Opportunity

[Nick Sabalausky]

On Tue, 09 Apr 2013 14:22:21 -0400
"Jonathan M Davis" <jmdavisProg at gmx.com> wrote:
> 
> If it's something that has to be
> fixed, it should be an error, and if it doesn't have to be fix, don't
> warn about it, because any good programmer is going to have to fix
> all of the warnings anyway, ultimately making it not much different
> from an error anyway. Stuff like you're suggesting really should be
> left up to lint-like tools.
> 

The way I see it, warnings *are* a lint tool. (Which is part of why I've
always disliked -w and use -wi instead.)