Wish: Variable Not Used Warning

[Markus Koskimies]

On Wed, 09 Jul 2008 13:41:35 -0700, Walter Bright wrote:

> Nick Sabalausky wrote:
>> "Walter Bright" <newshound1 at digitalmars.com> wrote in message
>> news:g530j8$18th$1 at digitalmars.com...
>>> The reason for treating warnings as errors when warnings are enabled
>>> is so that, for a long build, they don't scroll up and off your screen
>>> and go unnoticed.
>> 
>> Pardon me for saying so, but that doesn't sound like a very convincing
>> reason to turn every warning (which, by it's very nature, is something
>> that might not be a bug) into something that splits the language into
>> what are effectively different languages.
> 
> If you turn warnings on, then you want to see them and presumably deal
> with them. If you don't deal with them, then they persist every time you
> compile, and either they get very irritating and you fix them anyway, or
> you develop a blind spot for them and never see the ones you do want to
> fix.

I completely agree with this. If warnings are generated, it's best to 
stop compilation and let the developer to correct those parts.

Warnings, that does not stop building process have no use at all.