logo
Free, unlimited AI code reviews that run on commit
git-lrc git-lrc GitHub Install Now We'd appreciate a star git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt

Perl::Critic::Policy::TestingAndDebugging::RequireUseStrict - Always "use strict".

Affiliation

       This Policy is part of the core Perl::Critic distribution.

Author

       Jeffrey Ryan Thalhammer <jeff@imaginative-software.com>

Configuration

       If you make use of things like Moose::Exporter, you can create your own modules that import the strict
       pragma into the code that is "use"ing them.  There is an option to add to the default set of pragmata and
       modules in your .perlcriticrc: "equivalent_modules".

           [TestingAndDebugging::RequireUseStrict]
           equivalent_modules = MooseX::My::Sugar

Description

       Using strictures is probably the single most effective way to improve the quality of your code.  This
       policy requires that the 'use strict' statement must come before any other statements except "package",
       "require", and other "use" statements.  Thus, all the code in the entire package will be affected.

       There are special exemptions for Moose, Moose::Role, and Moose::Util::TypeConstraints because they
       enforces strictness; e.g.  'use Moose' is treated as equivalent to 'use strict'.

       The maximum number of violations per document for this policy defaults to 1.

Name

       Perl::Critic::Policy::TestingAndDebugging::RequireUseStrict - Always "use strict".

See Also

       Perl::Critic::Policy::TestingAndDebugging::ProhibitNoStrict

See Also