Manual Reference Pages - PERL::CRITIC::POLICY::TESTINGANDDEBUGGING::REQUIREUSEWARNINGS (3)
Perl::Critic::Policy::TestingAndDebugging::RequireUseWarnings - Always "use warnings".
This Policy is part of the core Perl::Critic
Using warnings, and paying attention to what they say, is probably the
single most effective way to improve the quality of your code. This
policy requires that the use warnings statement must come before
any other statements except package, require, and other use
statements. Thus, all the code in the entire package will be
There are special exemptions for Moose,
they enforces warnings; e.g. use Moose is treated as
equivalent to use warnings.
This policy will not complain if the file explicitly states that it is
compatible with a version of perl prior to 5.6 via an include
statement, e.g. by having require 5.005 in it.
The maximum number of violations per document for this policy defaults
If you make use of things like
Moose::Exporter, you can create your own modules
that import the warnings pragma into the code that is
useing them. There is an option to add to the default set of
pragmata and modules in your .perlcriticrc: equivalent_modules.
equivalent_modules = MooseX::My::Sugar
Needs to check for -w on the shebang line.
Jeffrey Ryan Thalhammer <firstname.lastname@example.org>
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.20.3 ||PERL::CRITIC::POLICY::TESTINGANDDEBUGGING::REQUIREUSEWARNINGS (3) ||2016-04-03 |
Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.