Hi
Matz mentioned that to supress the world writable message
(other than to actually fix the problem) was to use the
’-W0’ option when calling ruby. (#!/usr/bin/ruby -W0)
Is there a way to set this inside ruby?
Hi
Matz mentioned that to supress the world writable message
(other than to actually fix the problem) was to use the
’-W0’ option when calling ruby. (#!/usr/bin/ruby -W0)
Is there a way to set this inside ruby?
Hi
Matz mentioned that to supress the world writable message
(other than to actually fix the problem) was to use the
‘-W0’ option when calling ruby. (#!/usr/bin/ruby -W0)
Is there a way to set this inside ruby?
$-w = nil
works for me.
Thanks. I guess I didn’t try enough cases:
ruby -W0 -e ‘p $-w’
nil
ruby -W1 -e ‘p $-w’
false
ruby -W2 -e ‘p $-w’
true
ruby -W3 -e ‘p $-w’
true
BTW, is there a more readable version instead of the Perlism?
On Tuesday, 17 February 2004 at 23:04:53 +0900, fmccor@inforead.com wrote:
Jim Freeze jim@freeze.org wrote:
Hi
Matz mentioned that to supress the world writable message
(other than to actually fix the problem) was to use the
‘-W0’ option when calling ruby. (#!/usr/bin/ruby -W0)Is there a way to set this inside ruby?
$-w = nil
works for me.
History is curious stuff
You’d think by now we had enough
Yet the fact remains I fear
They make more of it every year.
Hi,
Jim Freeze jim@freeze.org writes:
ruby -W0 -e ‘p $-w’
nil
ruby -W1 -e ‘p $-w’
false
ruby -W2 -e ‘p $-w’
true
ruby -W3 -e ‘p $-w’
trueBTW, is there a more readable version instead of the Perlism?
% ruby -W0 -e ‘p $VERBOSE’
nil
% ruby -W1 -e ‘p $VERBOSE’
false
% ruby -W2 -e ‘p $VERBOSE’
true
–
eban