There are good reasons for disabling certain kinds of warnings. But if you were wise enough to use warnings in the first place, then it doesn't make sense to disable them completely. By default, any no warnings statement will violate this policy. However, you can configure this Policy to allow certain types of warnings to be disabled (See Configuration). A bare no warnings statement will always raise a violation.


The permitted warning types can be configured via the allow option. The value is a list of whitespace-delimited warning types that you want to be able to disable. See the perllexwarn manpage for a list of possible warning types. An example of this customization:

  allow = uninitialized once


the Perl::Critic::Policy::TestingAndDebugging::RequireUseWarnings manpage


Jeffrey Ryan Thalhammer <thaljef@cpan.org>


Copyright (c) 2005-2007 Jeffrey Ryan Thalhammer. All rights reserved.

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of this license can be found in the LICENSE file included with this module