From: Guillaume Marcais <guslist@...>
Date: 2003-07-10T00:26:30+09:00
Subject: Re: Array.each

Same idea as when I program in C: I do gcc -Wall ... Some warnings are
not actual errors, but of them are and it helps me get my program
straight. But I write in such a way that no warnings are display during
compilation.

That's what I would do with ruby. During my develpment cycle I would
consider warnings as errors and remove them. In production, leave it as
a warning, no need for the application to crash if not needed...

Guillaume.

On Wed, 2003-07-09 at 10:48, ts wrote:
> >>>>> "B" == Brian Candler <B.Candler@pobox.com> writes:
> 
> B> The fact that the error is not trapped at the earliest possible point, but
> B> may result in a failure downstream (possibly a long way downstream)
> 
>  a warning is not an error.
> 
> 
> Guy Decoux
> 
>