Comments on: Temporarily disabling warnings in Ruby

By: David Cuadrado

David Cuadrado — Wed, 18 Jul 2012 16:05:00 +0000

$-v = true is simpler.

By: Avdi Grimm

Avdi Grimm — Mon, 29 Aug 2011 03:23:00 +0000

By: nicholas a. evans

nicholas a. evans — Fri, 26 Aug 2011 11:17:00 +0000

Ruby’s $VERBOSE would be *so* much more useful if it could be enabled or disabled on a per-file basis.

By: raggi

raggi — Thu, 25 Aug 2011 16:56:00 +0000

$VERBOSE = false and $VERBOSE = nil mean different things.

Only $VERBOSE = nil will squash interpreter warnings. $VERBOSE = false will squash Kernel.warn

By: Eric Anderson

Eric Anderson — Thu, 25 Aug 2011 16:07:00 +0000

There is also $VERBOSE = false if you don’t want to redirect stderr (maybe the library uses stderr for something useful).

Although testing your messy.rb I found that $VERBOSE = false still complained about the constant redefinition. So your method is more complete. But if you need stderr to work then $VERBOSE = false is nice (of course you can turn on warnings with $VERBOSE = true).

Rails uses this method in it’s implementation of “silence_warnings”.

By: JEG2

JEG2 — Thu, 25 Aug 2011 16:05:00 +0000

Ruby has a variable for controlling the warnings level, called $VERBOSE. We can just use this by saving it’s value at the beginning of the method (old_verbose, $VERBOSE = $VERBOSE, nil) and restoring it in the ensure clause ($VERBOSE = old_verbose).

By: Aaron Patterson

Aaron Patterson — Thu, 25 Aug 2011 16:03:00 +0000

You are a terrible, terrible person. ;-)