Re: -Wall

> > I never said that warnings are a bad thing. It's a good tool for
> > developers.
> 
> (I wasn't confroning you personally, if that's how you interpreted it.)
No problem :)

> > I just said that end users do not necessarily have to see them. A
> > developer might not mind but an end user might wonder that these
> > strange warnings are, whether Ruby will work fine or not...
> 
> How often do end users actually see these errors?  And if they
> do, they're probably curious enough to actually want to see them and
> perhaps they'll even report them to the developers, when they do.
Not very often, that's true :).
But it's not up to me to take the decision. I was just trying to
defend the current default, and the possible reasons I saw for it.
For the real reasons and the final answer I think we will have to wait
for some Japanese people to wake up tomorrow morning ;).

Cheers,
Vincent Isambart