perl::critic::policy::testinganddebugging::prohibitnostrict(3) [centos man page]
Perl::Critic::Policy::TestingAndDebugging::ProhibitNoStrUser3Contributed Perl DocumePerl::Critic::Policy::TestingAndDebugging::ProhibitNoStrict(3) NAME
Perl::Critic::Policy::TestingAndDebugging::ProhibitNoStrict - Prohibit various flavors of "no strict". AFFILIATION
This Policy is part of the core Perl::Critic distribution. DESCRIPTION
There are good reasons for disabling certain kinds of strictures, But if you were wise enough to "use strict" in the first place, then it doesn't make sense to disable it completely. By default, any "no strict" statement will violate this policy. However, you can configure this Policy to allow certain types of strictures to be disabled (See "CONFIGURATION"). A bare "no strict" statement will always raise a violation. CONFIGURATION
The permitted strictures can be configured via the "allow" option. The value is a list of whitespace-delimited stricture types that you want to permit. These can be "vars", "subs" and/or "refs". An example of this customization: [TestingAndDebugging::ProhibitNoStrict] allow = vars subs refs SEE ALSO
Perl::Critic::Policy::TestingAndDebugging::RequireUseStrict AUTHOR
Jeffrey Ryan Thalhammer <jeff@imaginative-software.com> COPYRIGHT
Copyright (c) 2005-2011 Imaginative Software Systems. 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 perl v5.16.3 2014-06-09 Perl::Critic::Policy::TestingAndDebugging::ProhibitNoStrict(3)
Check Out this Related Man Page
Perl::Critic::Policy::TestingAndDebugging::ProhibitNoWarUsersContributed Perl DocuPerl::Critic::Policy::TestingAndDebugging::ProhibitNoWarnings(3) NAME
Perl::Critic::Policy::TestingAndDebugging::ProhibitNoWarnings - Prohibit various flavors of "no warnings". AFFILIATION
This Policy is part of the core Perl::Critic distribution. DESCRIPTION
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. CONFIGURATION
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 perllexwarn for a list of possible warning types. An example of this customization: [TestingAndDebugging::ProhibitNoWarnings] allow = uninitialized once If a true value is specified for the "allow_with_category_restriction" option, then any "no warnings" that restricts the set of warnings that are turned off will pass. [TestingAndDebugging::ProhibitNoWarnings] allow_with_category_restriction = 1 SEE ALSO
Perl::Critic::Policy::TestingAndDebugging::RequireUseWarnings AUTHOR
Jeffrey Ryan Thalhammer <jeff@imaginative-software.com> COPYRIGHT
Copyright (c) 2005-2011 Imaginative Software Systems. 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 perl v5.16.3 2014-06-09 Perl::Critic::Policy::TestingAndDebugging::ProhibitNoWarnings(3)