On Tue, 28 Mar 2006, Justin Collins wrote:

> Wybo Dekker wrote:
>> I would like to use the -w commandline option always, but any useful output 
>> is always obscured by message from the standard libraries:
>> 
>> For example:
>>
>> [messages skipped] 
>> 
>> Should such messages not be banned?
>> 
>
> Some warnings are really just informational. For example, redefining a method 
> isn't 'wrong,' and it can be how your program is supposed to function. Or 
> having an uninitialized instance variable might not matter - after all, I 
> don't think there is a difference between that and setting it to nil.
>
> However, it could be dangerous or unintentional, so you get a warning. As 
> with all debugging output, you have to filter through it sometimes.

Sure, that's all true, and I want to see such messages to warn myself for 
possibly bad programming habits.
But when I see lots of such message emerge from libraries that I didn't 
write myself, I'll easily miss the ones that really matter to me and can 
be influenced by me.

-- 
Wybo