Perl::Critic::Policy - Base class for all Policy modules. River stage four • 109 direct dependents • 1173 total dependents

Perl::Critic::Policy is the abstract base class for all Policy objects. If you're developing your own Policies, your job is to implement and override its methods in a subclass. To work with the Perl::Critic engine, your implementation must behave as ...

PETDANCE/Perl-Critic-1.132 - 01 Jun 2018 03:03:22 GMT

Test::Perl::Critic::Policy - A framework for testing your custom Policies River stage four • 109 direct dependents • 1173 total dependents

This module provides a framework for function-testing your custom Perl::Critic::Policy modules. Policy testing usually involves feeding it a string of Perl code and checking its behavior. In the old days, those strings of Perl code were mixed directl...

PETDANCE/Perl-Critic-1.132 - 01 Jun 2018 03:03:22 GMT

Perl::Critic::Policy::Perlsecret - Prevent perlsecrets entering your codebase River stage zero No dependents

This policy checks for perlsecret operators in your code and warns you about them. You can override the secrets that are allowed or disallowed using the parameters "allow_secrets" and "disallow_secrets". The default is to simply disallow everything. ...

LANCEW/Perl-Critic-Policy-Perlsecret-0.0.11 - 05 Jan 2017 20:45:37 GMT

Perl::Critic::Policy::BadStrings - Search for bad strings in source files River stage zero No dependents

This policy will search for "bad words" in a file. It does this by looking at the raw Perl file, so the "bad words" can include different types of elements. The obvious use for this module would be to search for obscene words, but it can also be used...

JMASLAK/Perl-Critic-Policy-BadStrings-1.000 - 25 Nov 2017 16:22:09 GMT

Perl::Critic::Policy::CompileTime - Provide Perl::Critic support for hunting down compile-time side effects River stage zero No dependents

Perl::Critic::Policy::CompileTime is a Perl::Critic module which allows one to quickly find code in a large codebase or installation which may not run the way one expects when compiled by the Perl compiler, B::C. With the help of the underlying code ...

XAN/Perl-Critic-Policy-CompileTime-0.03 - 26 Sep 2014 20:34:02 GMT

Perl::Critic::Policy::HTTPCookies - Avoid using HTTP::Cookies River stage zero No dependents

This module provides Perl::Critic policies to detect the use of HTTP::Cookies. HTTP::Cookies takes a very lenient approach to setting cookies that does not work well with today's Internet: <https://github.com/libwww-perl/http-cookies/pull/7> Consider...

TOMHUKINS/Perl-Critic-Policy-HTTPCookies-0.53 - 04 Jan 2017 18:50:14 GMT

Perl::Critic::Policy::ProhibitSmartmatch River stage zero No dependents

This distribution provides two Perl::Critic policies which help to avoid both explicit and implicit smartmatching....

HOLCAPEK/Perl-Critic-Policy-ProhibitSmartmatch-0.4 - 08 Dec 2017 08:44:38 GMT

Perl::Critic::Policy::Freenode::Each - Don't use each to iterate through a hash River stage one • 2 direct dependents • 3 total dependents

The "each()" function relies on an iterator internal to a hash (or array), which is the same iterator used by "keys()" and "values()". So deleting or adding hash elements during iteration, or just calling "keys()" or "values()" on the hash, will caus...

DBOOK/Perl-Critic-Freenode-0.028 - 30 Nov 2018 00:33:24 GMT

Perl::Critic::Policy::Freenode::ModPerl - Don't use mod_perl to write web applications River stage one • 2 direct dependents • 3 total dependents

mod_perl <http://perl.apache.org/> is an embedded Perl interpreter for the Apache <http://www.apache.org/> web server. It allows you to dynamically configure and mod Apache. It is not a generally good solution for writing web applications. Frameworks...

DBOOK/Perl-Critic-Freenode-0.028 - 30 Nov 2018 00:33:24 GMT

Perl::Critic::Policy::Freenode::Threads - Interpreter-based threads are officially discouraged River stage one • 2 direct dependents • 3 total dependents

Perl interpreter threads are officially discouraged. They were created to emulate "fork()" in Windows environments, and are not fast or lightweight as one may expect. Non-blocking code or I/O can be easily parallelized by using an event loop such as ...

DBOOK/Perl-Critic-Freenode-0.028 - 30 Nov 2018 00:33:24 GMT

Perl::Critic::Policy::OTRS::ProhibitOpen - Do not use "open" River stage one • 1 direct dependent • 1 total dependent

RENEEB/Perl-Critic-OTRS-0.08 - 03 Jul 2018 08:22:48 GMT

Perl::Critic::Policy::Freenode::OpenArgs - Always use the three-argument form of open River stage one • 2 direct dependents • 3 total dependents

The "open()" function may be called in a two-argument form where the filename is parsed to determine the mode of opening, which may include piping input or output. (In the one-argument form, this filename is retrieved from a global variable, but the ...

DBOOK/Perl-Critic-Freenode-0.028 - 30 Nov 2018 00:33:24 GMT

Perl::Critic::Policy::Freenode::DollarAB - Don't use $a or $b as variable names outside sort River stage one • 2 direct dependents • 3 total dependents

The special variables $a and $b are reserved for "sort()" and similar functions which assign to them to iterate over pairs of values. These are global variables, and declaring them as lexical variables with "my" to use them outside this context can b...

DBOOK/Perl-Critic-Freenode-0.028 - 30 Nov 2018 00:33:24 GMT

Perl::Critic::PolicyBundle::PERLANCAR - Perl::Critic policies River stage one • 1 direct dependent • 1 total dependent

PERLANCAR/Perl-Critic-PolicyBundle-PERLANCAR-0.002 - 16 Aug 2017 11:37:53 GMT

Perl::Critic::Policy::Freenode::Wantarray - Don't write context-sensitive functions using wantarray River stage one • 2 direct dependents • 3 total dependents

Context-sensitive functions, while one way to write functions that DWIM (Do What I Mean), tend to instead lead to unexpected behavior when the function is accidentally used in a different context, especially if the function's behavior changes signifi...

DBOOK/Perl-Critic-Freenode-0.028 - 30 Nov 2018 00:33:24 GMT

Perl::Critic::Policy::Dynamic::NoIndirect - Perl::Critic policy against indirect method calls. River stage one • 1 direct dependent • 1 total dependent

This Perl::Critic dynamic policy reports any use of indirect object syntax with a 'stern' severity. It's listed under the 'dynamic' and 'maintenance' themes. Since it wraps around indirect, it needs to compile the audited code and as such is implemen...

VPIT/Perl-Critic-Policy-Dynamic-NoIndirect-0.06 - 25 Aug 2011 14:55:26 GMT

Perl::Critic::Policy::TryTiny::RequireUse - Requires that code which utilizes Try::Tiny actually use()es it. River stage zero No dependents

A common problem with Try::Tiny is forgetting to use the module in the first place. For example: perl -e 'try { print "hello" } catch { print "world" }' Can't call method "catch" without a package or object reference at -e line 1. helloworld If you f...

BLUEFEET/Perl-Critic-Policy-TryTiny-RequireUse-0.03 - 20 Jul 2018 19:10:52 GMT

Perl::Critic::Policy::OTRS::ProhibitDumper - Check module for use of "Dumper" River stage one • 1 direct dependent • 1 total dependent

RENEEB/Perl-Critic-OTRS-0.08 - 03 Jul 2018 08:22:48 GMT

Perl::Critic::Policy::Freenode::LoopOnHash - Don't loop over hashes River stage one • 2 direct dependents • 3 total dependents

It's possible to loop over a hash as if it was a list, which results in alternating between the keys and values of the hash. Often, the intent was instead to loop over either the keys or the values of the hash. foreach my $foo (%hash) { ... } # not o...

DBOOK/Perl-Critic-Freenode-0.028 - 30 Nov 2018 00:33:24 GMT

Perl::Critic::Policy::Variables::NameReuse - Don't reuse names for different types of variables River stage zero No dependents

This policy checks for the existence of multiple variables with the same name in a file. This can be confusing especially when accessing elements of variables or using list or key-value slices. For example, the code could access both $foo and $foo[0]...

DBOOK/Perl-Critic-Policy-Variables-NameReuse-v0.1.0 - 29 Nov 2018 02:18:04 GMT

376 results (0.051 seconds)