From: "Timothy J. Wood" <tjw@...>
Date: 2006-02-08T01:00:29+09:00
Subject: Re: [RCR] ruby --quiet; was Re: ANDCALL / iff? / &? (was Re: ruby-dev summary 28206-28273)


On Feb 7, 2006, at 7:05 AM, ara.t.howard@noaa.gov wrote:
> i agree.  however -w should not be changed.  simply do
>
>   $VERBOSE=nil
>
> and you will get no warnings.  i use it often due to ruby's over- 
> zealous
> warnings

   These two statements seem contradictory to me.  If -w is useful,  
then it shouldn't be turned off.  If it isn't useful, then it  
shouldn't exist (or should be fixed).

   How about the same idiom as in gcc for this particular case?

	if a = b # warns
		...
	end

	if (a = b) # doesn't warn
		...
	end

   Better yet have warnings be individually configurable:

	ruby -w # all warnings on
	ruby -w -wno_assign_in_conditional # everything but this warning

	# Or, at runtime...
	$WARNINGS[:assign_in_conditional] = false

   I admit, I'm a warning zealot and compile my C code with '-Wall - 
Werror -Weverything-not-included-inWall' ... :)

-tim