Forum: Ruby how to ignore warning

how to ignore warning messages in ruby (when executing ruby code)

Quoth Pokkai Dokkai:
> how to ignore warning messages in ruby (when executing ruby code)

Close your eyes and tap your heels thrice.
No, really, ignoring things is as easy as not looking at them. (In all
likelihood you should fix your code to not have warnings instead.)

Regards,

On 11 Oct 2007, at 12:26, Konrad Meyer wrote:

> Quoth Pokkai Dokkai:
>> how to ignore warning messages in ruby (when executing ruby code)
>
> Close your eyes and tap your heels thrice.
> No, really, ignoring things is as easy as not looking at them. (In all
> likelihood you should fix your code to not have warnings instead.)

I agree with Konrad that you should probably fix warnings rather than
ignore, but -W is the command line flag you want. -W1 is standard, -
W2 is verbose, -W0 is no warnings whatsoever.

Alex Gutteridge

Bioinformatics Center
Kyoto University

Alex Gutteridge wrote:

> I agree with Konrad that you should probably fix warnings rather than
> ignore, but -W is the command line flag you want. -W1 is standard, -
> W2 is verbose, -W0 is no warnings whatsoever.
> 
> Alex Gutteridge
> 
> Bioinformatics Center
> Kyoto University

thank you Alex

Alex Gutteridge wrote:
> -W is the command line flag you want. -W1 is standard, -
> W2 is verbose, -W0 is no warnings whatsoever.

Is there a possibility to ignore warnings dynamically? - I mean, 
sometimes it's helpful to redefine constants, which will always produce 
a warning. I want to suppress warnings for these lines only.

Wolfgang Nádasi-Donner

Hi,

Am Donnerstag, 11. Okt 2007, 12:48:22 +0900 schrieb Alex Gutteridge:
> -W1 is standard, -W2 is 
> verbose, -W0 is no warnings whatsoever.

Or set one of the variables $-v, $-w, $VERBOSE to 'nil'.

   Option    $-v
   -W0       nil
   -W1       false
   -W2       true

Bertram

Hi,

Am Donnerstag, 11. Okt 2007, 19:22:31 +0900 schrieb Wolfgang 
Nádasi-Donner:
> Alex Gutteridge wrote:
> > -W is the command line flag you want. -W1 is standard, -
> > W2 is verbose, -W0 is no warnings whatsoever.
> 
> Is there a possibility to ignore warnings dynamically? - I mean, 
> sometimes it's helpful to redefine constants, which will always produce 
> a warning. I want to suppress warnings for these lines only.


  irb(main):001:0> X = "x"
  => "x"
  irb(main):002:0> class Object ; remove_const :X ; end
  => "x"
  irb(main):003:0> X
  NameError: uninitialized constant X
          from (irb):3
  irb(main):004:0> X = "y"
  => "y"
  irb(main):005:0>


Bertram

Bertram Scharpf wrote:
>   irb(main):001:0> X = "x"
>   => "x"
>   irb(main):002:0> class Object ; remove_const :X ; end
>   => "x"
>   irb(main):003:0> X
>   NameError: uninitialized constant X
>           from (irb):3
>   irb(main):004:0> X = "y"
>   => "y"
>   irb(main):005:0>

Well - it looks fine, because it's no dirty trick.

Wolfgang Nádasi-Donner

On 10/10/07, Konrad Meyer <konrad@tylerc.org> wrote:
> Quoth Pokkai Dokkai:
> > how to ignore warning messages in ruby (when executing ruby code)
>
> Close your eyes and tap your heels thrice.
> No, really, ignoring things is as easy as not looking at them.

Or cover your head with your towel, rubyists should ALWAYS have their
towel handy.

And as the Hitchhiker's Guide to Ruby explains this is also the best
defense against being eaten by the ravenous bugblatter beast of Traal!
--
Rick DeNatale

My blog on Ruby
http://talklikeaduck.denhaven2.com/

Bertram Scharpf wrote:
> 
>   irb(main):001:0> X = "x"
>   => "x"
>   irb(main):002:0> class Object ; remove_const :X ; end
>   => "x"
>   irb(main):003:0> X
>   NameError: uninitialized constant X
>           from (irb):3
>   irb(main):004:0> X = "y"
>   => "y"
>   irb(main):005:0>

Yuck.

I've pushed for structured warnings in the past, but it has fallen on
deaf ears.

See:

http://osdir.com/ml/lang.ruby.sydney.devel/2005-10/msg00009.html
http://osdir.com/ml/lang.ruby.sydney.devel/2005-10/msg00010.html
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/50105

Regards,

Dan

Rick Denatale wrote:
> Or cover your head with your towel, rubyists should ALWAYS have their
> towel handy.
> 
> And as the Hitchhiker's Guide to Ruby explains this is also the best
> defense against being eaten by the ravenous bugblatter beast of Traal!
> --
> Rick DeNatale
> 
> My blog on Ruby
> http://talklikeaduck.denhaven2.com/

likin' it :)

Konrad Meyer wrote:
> Quoth Pokkai Dokkai:
>> how to ignore warning messages in ruby (when executing ruby code)
> 
> Close your eyes and tap your heels thrice.
> No, really, ignoring things is as easy as not looking at them. (In all
> likelihood you should fix your code to not have warnings instead.)
> 
> Regards,

Ruby will spit out warnings for white space  -  with no coding errors,

and many programming languages output warnings for using anything but 
the most basic techniques

so weather you're a novice or a seasoned veteran there are valid reasons 
to suppress warnings:  after all, it does have W levels