Search results for "module:Perl::Critic::Policy::Modules::RequireExplicitPackage"

Perl::Critic::Policy::Modules::RequireExplicitPackage - Always make the package explicit. River stage three • 131 direct dependents • 386 total dependents

In general, the first statement of any Perl module or library should be a "package" statement. Otherwise, all the code that comes before the "package" statement is getting executed in the caller's package, and you have no idea who that is. Good encap...

PETDANCE/Perl-Critic-1.142 - 29 Nov 2022 02:20:23 UTC

Perl::Critic::Policy::Modules::RequireExplicitPackage::ObjectPad - Always make the package/Object::Pad class explicit. River stage zero No dependents

DERIV/Perl-Critic-Policy-Modules-RequireExplicitPackage-ObjectPad-0.001 - 09 Aug 2022 14:29:44 UTC

Perl::Critic::Policy::Modules::RequireEndWithOne - End each module with an explicitly 1; instead of some funky expression. River stage three • 131 direct dependents • 386 total dependents

All files included via "use" or "require" must end with a true value to indicate to the caller that the include was successful. The standard practice is to conclude your .pm files with "1;", but some authors like to get clever and return some other t...

PETDANCE/Perl-Critic-1.142 - 29 Nov 2022 02:20:23 UTC

Perl::Critic::Policy::Lax::RequireExplicitPackage::ExceptForPragmata - you can put strict and warnings before "package" River stage two • 6 direct dependents • 12 total dependents

This policy is meant to replace Modules::RequireExplicitPackage. That policy's POD says: In general, the first statement of any Perl module or library should be a package statement. Otherwise, all the code that comes before the package statement is g...

RJBS/Perl-Critic-Lax-0.013 - 13 Mar 2017 12:34:51 UTC
4 results (0.066 seconds)