Suppress "mytime redefined" message from Benchmark?

[Jeff Boes]

Hmm ... this one's got me puzzled:

$ perl -v


This is perl, v5.8.3 built for i686-linux

....

$ perl -w -e 'no warnings; use Benchmark qwhireswallclock)'
Subroutine Benchmark::mytime redefined at
/usr/local/lib/perl5/5.8.3/Benchmark.pm line 456.

$ perl -w -e 'no warnings qw(redefine); use Benchmark qwhireswallclock)'
Subroutine Benchmark::mytime redefined at
/usr/local/lib/perl5/5.8.3/Benchmark.pm line 456.


Does anyone know of a way to completely suppress this warning? It's
irritating, because I have a script running in cron that reports this
message, over and over. (I don't want to suppress or redirect STDERR,
because there may be other legitimate errors.)

 

[Malcolm Dew-Jones]

Jeff Boes ([email protected]) wrote:
: Hmm ... this one's got me puzzled:

: $ perl -v
:

: This is perl, v5.8.3 built for i686-linux

: ...

: $ perl -w -e 'no warnings; use Benchmark qwhireswallclock)'
: Subroutine Benchmark::mytime redefined at
: /usr/local/lib/perl5/5.8.3/Benchmark.pm line 456.

: $ perl -w -e 'no warnings qw(redefine); use Benchmark qwhireswallclock)'
: Subroutine Benchmark::mytime redefined at
: /usr/local/lib/perl5/5.8.3/Benchmark.pm line 456.


: Does anyone know of a way to completely suppress this warning? It's
: irritating, because I have a script running in cron that reports this
: message, over and over. (I don't want to suppress or redirect STDERR,
: because there may be other legitimate errors.)


$SIG{__WARN__}

Examine the warnings and skip the one you don't want.

 

[Darren Dunham]

$ perl -w -e 'no warnings; use Benchmark qwhireswallclock)'
Subroutine Benchmark::mytime redefined at
/usr/local/lib/perl5/5.8.3/Benchmark.pm line 456.

$ perl -w -e 'no warnings qw(redefine); use Benchmark qwhireswallclock)'
Subroutine Benchmark::mytime redefined at
/usr/local/lib/perl5/5.8.3/Benchmark.pm line 456.

Both of those attempts won't work because the 'no warnings' isn't read
until runtime, while the 'use' is done earlier.

Is this a bug with Benchmark? I suppose you could report it.

Add your 'no warnings qw(redefine)' to Benchmark.pm between 455 and 456.

 

[John W. Krahn]

Hmm ... this one's got me puzzled:

$ perl -v

This is perl, v5.8.3 built for i686-linux

$ perl -w -e 'no warnings; use Benchmark qwhireswallclock)'
Subroutine Benchmark::mytime redefined at
/usr/local/lib/perl5/5.8.3/Benchmark.pm line 456.

$ perl -w -e 'no warnings qw(redefine); use Benchmark qwhireswallclock)'
Subroutine Benchmark::mytime redefined at
/usr/local/lib/perl5/5.8.3/Benchmark.pm line 456.

Does anyone know of a way to completely suppress this warning? It's
irritating, because I have a script running in cron that reports this
message, over and over. (I don't want to suppress or redirect STDERR,
because there may be other legitimate errors.)

The warnings pragma and the -w switch are incompatible.

perldoc perllexwarn


John

 

[Gunnar Hjalmarsson]

$ perl -w -e 'no warnings; use Benchmark qwhireswallclock)'
Subroutine Benchmark::mytime redefined at
/usr/local/lib/perl5/5.8.3/Benchmark.pm line 456.

Does anyone know of a way to completely suppress this warning? It's
irritating, because I have a script running in cron that reports
this message, over and over. (I don't want to suppress or redirect
STDERR, because there may be other legitimate errors.)

The -w switch is dynamically scoped, which means that it enables all
kinds of warnings also in modules that you use or require. The
warnings pragma is lexically scoped, so 'no warnings' only switches
off the warnings in the current file.

I suppose that the best solution is to drop the -w switch and enable
warnings lexically by doing

use warnings;

 

[Jay Tilton]

: > $ perl -w -e 'no warnings; use Benchmark qwhireswallclock)'
: > Subroutine Benchmark::mytime redefined at
: > /usr/local/lib/perl5/5.8.3/Benchmark.pm line 456.
:
: > $ perl -w -e 'no warnings qw(redefine); use Benchmark qwhireswallclock)'
: > Subroutine Benchmark::mytime redefined at
: > /usr/local/lib/perl5/5.8.3/Benchmark.pm line 456.
:
: Both of those attempts won't work because the 'no warnings' isn't read
: until runtime, while the 'use' is done earlier.

Poppycock. 'use' and 'no' both happen during compilation.