in reply to Re: Re: Re: Triggering 'strict' from within a package
in thread Triggering 'strict' from within a package

I still don't understand. Is there any case where strict merely produces a warning?

What I'm talking about is strict failing a program at run-time, and then dumping stuff in the logs, viz:

Global symbol "$foo" requires explicit package name at /home/user/www/test.pl line 10.

.. it's getting rid of that kind of stuff that I'm talking about (I don't think warnings makes any difference in that case?)

  • Comment on Re: Re: Re: Re: Triggering 'strict' from within a package

Replies are listed 'Best First'.
Re^5: Triggering 'strict' from within a package
by Aristotle (Chancellor) on Aug 12, 2002 at 23:36 UTC
    This is no reason to disable strictures, it is a reason to use CGI::Carp's carpout() or set_message() functions. Disabling strictures is a serious mistake especially on a production server where failing a stricture at runtime should be indicative of a critical bug. In such a case, you want strict to scream bloody murder and kill your script rather than the script being able to run on and silently throw sand into your machinery.

    Makeshifts last the longest.

[reply]

In Section Seekers of Perl Wisdom