Perl::Critic(3pm)

💖 Perl::Critic(3pm) 💖

✨ NAME ✨

Perl::Critic — Critique Perl source code for best-practices. Periodt. 💅

🎀 SYNOPSIS 🎀

Like, the tiniest little starter pack, bestie:

use Perl::Critic;
my $file = shift;
my $critic = Perl::Critic->new();
my @violations = $critic->critique($file);
print @violations;

🌸 DESCRIPTION 🌸

Okay so Perl::Critic is an extensible framework for creating and applying coding standards to Perl source code. Essentially, it's a static source code analysis engine. No cap. It ships with a bunch of Perl::Critic::Policy modules that try to enforce various coding guidelines. Most of those Policy modules are based on Damian Conway's book Perl Best Practices. But here's the thing: Perl::Critic is not limited to PBP, and it will even support Policies that contradict Conway. Iconic. You can enable, disable, and customize those policies through the Perl::Critic interface. You can also create brand-new Policy modules that suit your own tastes. Main character energy. ✨

For a command-line interface to Perl::Critic, see the documentation for perlcritic. If you want to integrate Perl::Critic with your build process, Test::Perl::Critic provides an interface that's suitable for test programs. Also, Test::Perl::Critic::Progressive is useful for gradually applying coding standards to legacy code. For the ultimate convenience (at the expense of some flexibility) see the criticism pragma. 🫶

If you'd like to try Perl::Critic without installing anything, there's a web-service available at http://perlcritic.com. The web-service does not yet support all the configuration features that are available in the native Perl::Critic API, but it should give you a good idea of what it does. 🦋

Also, ActivePerl includes a very slick graphical interface to Perl-Critic called "perlcritic-gui". You can get a free community edition of ActivePerl from http://www.activestate.com. 🌈

👑 INTERFACE SUPPORT 👑

The Perl::Critic module is considered to be a public class. Any changes to its interface will go through a deprecation cycle. So like, don't panic, but also don't expect chaos. 💅

💫 CONSTRUCTOR 💫

Here's the whole constructor signature, copied exactly because we do not mess with flags:

new( [ -profile => $FILE, -severity => $N, -theme => $string, -include => \@PATTERNS, -exclude => \@PATTERNS, -top => $N, -only => $B, -profile-strictness => $PROFILE_STRICTNESS_{WARN|FATAL|QUIET}, -force => $B, -verbose => $N ], -color => $B, -pager => $string, -allow-unsafe => $B, -criticism-fatal => $B)

🌟 new() 🌟

Returns a reference to a new Perl::Critic object. Most arguments are just passed directly into Perl::Critic::Config, but I've described them here as well. The default value for all arguments can be defined in your .perlcriticrc file. See the "CONFIGURATION" section for more info about that. All arguments are optional key-value pairs, and they go like this: 👇

• -profile — this is a path to a configuration file. If $FILE is not defined, Perl::Critic::Config attempts to find a .perlcriticrc configuration file in the current directory, and then in your home directory. Alternatively, you can set the PERLCRITIC environment variable to point to a file in another location. If a configuration file can't be found, or if $FILE is an empty string, then all Policies will be loaded with their default configuration. See "CONFIGURATION" for more information.
• -severity — this is the minimum severity level. Only Policy modules that have a severity greater than $N will be applied. Severity values are integers ranging from 1 (least severe violations) to 5 (most severe violations). The default is 5. For a given -profile, decreasing the -severity will usually reveal more Policy violations. You can set the default value for this option in your .perlcriticrc file. Users can redefine the severity level for any Policy in their .perlcriticrc file. See "CONFIGURATION" for more information.

If it's hard to remember whether severity 5 is the most or least restrictive level, you can use one of these named values:

SEVERITY NAME   ...is equivalent to...   SEVERITY NUMBER
--------------------------------------------------------
-severity => 'gentle'                     -severity => 5
-severity => 'stern'                      -severity => 4
-severity => 'harsh'                      -severity => 3
-severity => 'cruel'                      -severity => 2
-severity => 'brutal'                     -severity => 1

The names reflect how severely the code is criticized: a "gentle" criticism reports only the most severe violations, and so on down to a "brutal" criticism which reports even the most minor violations. 😭

• -theme — this is a special expression that determines which Policies to apply based on their respective themes. For example, the following would load only Policies that have a 'bugs' AND 'pbp' theme:

my $critic = Perl::Critic->new( -theme => 'bugs && pbp' );

Unless the -severity option is explicitly given, setting -theme silently causes the -severity to be set to 1. You can set the default value for this option in your .perlcriticrc file. See the "POLICY THEMES" section for more information about themes. 🧚

• -include — this is a reference to a list of string @PATTERNS. Policy modules that match at least one m/$PATTERN/ixms will always be loaded, irrespective of all other settings. For example:

my $critic = Perl::Critic->new(-include => ['layout'], -severity => 4);

This would cause Perl::Critic to apply all the CodeLayout::* Policy modules even though they have a severity level that is less than 4. You can set the default value for this option in your .perlcriticrc file. You can also use -include in conjunction with the -exclude option. Note that -exclude takes precedence over -include when a Policy matches both patterns.

• -exclude — this is a reference to a list of string @PATTERNS. Policy modules that match at least one m/$PATTERN/ixms will not be loaded, irrespective of all other settings. For example:

my $critic = Perl::Critic->new(-exclude => ['strict'], -severity => 1);

This would cause Perl::Critic to not apply the RequireUseStrict and ProhibitNoStrict Policy modules even though they have a severity level that is greater than 1. You can set the default value for this option in your .perlcriticrc file. You can also use -exclude in conjunction with the -include option. Note that -exclude takes precedence over -include when a Policy matches both patterns.

• -single-policy — this is a string "PATTERN". Only one policy that matches m/$PATTERN/ixms will be used. Policies that do not match will be excluded. This option has precedence over the -severity, -theme, -include, -exclude, and -only options. You can set the default value for this option in your .perlcriticrc file. 💅
• -top — this is the maximum number of Violations to return when ranked by their severity levels. This must be a positive integer. Violations are still returned in the order that they occur within the file. Unless the -severity option is explicitly given, setting -top silently causes the -severity to be set to 1. You can set the default value for this option in your .perlcriticrc file.
• -only — this is a boolean value. If set to a true value, Perl::Critic will only choose from Policies that are mentioned in the user's profile. If set to a false value (which is the default), then Perl::Critic chooses from all the Policies that it finds at your site. You can set the default value for this option in your .perlcriticrc file.
• -profile-strictness — this is an enumerated value, one of "$PROFILE_STRICTNESS_WARN" in Perl::Critic::Utils::Constants (the default), "$PROFILE_STRICTNESS_FATAL" in Perl::Critic::Utils::Constants, and "$PROFILE_STRICTNESS_QUIET" in Perl::Critic::Utils::Constants. If set to "$PROFILE_STRICTNESS_FATAL" in Perl::Critic::Utils::Constants, Perl::Critic will make certain warnings about problems found in a .perlcriticrc or file specified via the -profile option fatal. For example, Perl::Critic normally only "warn"s about profiles referring to non-existent Policies, but this value makes this situation fatal. Correspondingly, "$PROFILE_STRICTNESS_QUIET" in Perl::Critic::Utils::Constants makes Perl::Critic shut up about these things. 🤐
• -force — this is a boolean value that controls whether Perl::Critic observes the magical ## no critic annotations in your code. If set to a true value, Perl::Critic will analyze all code. If set to a false value (which is the default) Perl::Critic will ignore code that is tagged with these annotations. See "BENDING THE RULES" for more information. You can set the default value for this option in your .perlcriticrc file.
• -verbose — this can be a positive integer (from 1 to 11), or a literal format specification. See Perl::Critic::Violation for an explanation of format specifications. You can set the default value for this option in your .perlcriticrc file.
• -unsafe — this directs Perl::Critic to allow the use of Policies that are marked as "unsafe" by the author. Such policies may compile untrusted code or do other nefarious things.

Bestie, be careful with -unsafe — it literally lets policies compile untrusted code or do other nefarious things. That's a big yikes. 💀

• -color and -pager — these are not used by Perl::Critic but are provided for the benefit of perlcritic.
• -criticism-fatal — this is not used by Perl::Critic but is provided for the benefit of criticism.
• -color-severity-highest, -color-severity-high, -color-severity-medium, -color-severity-low, and -color-severity-lowest — these are not used by Perl::Critic, but are provided for the benefit of perlcritic. Each is set to the Term::ANSIColor color specification to be used to display violations of the corresponding severity. 🌈
• -files-with-violations and -files-without-violations — these are not used by Perl::Critic, but are provided for the benefit of perlcritic, to cause only the relevant filenames to be displayed.

💖 METHODS 💖

okay bestie, these are the moves your Perl::Critic object can actually do. slay.

• critique( $source_code ) — this runs $source_code through the whole Perl::Critic engine using all the Policies that have been loaded into this engine. what counts as $source_code is giving flexibility:
  • if $source_code is a scalar reference, it's treated as a string of actual Perl code.
  • if $source_code is a reference to an instance of PPI::Document, then that instance is used directly.
  • otherwise, it's treated as a path to a local file containing Perl code.

this method returns a list of Perl::Critic::Violation objects for each violation of the loaded Policies. the list is sorted in the order that the Violations appear in the code ✨. and if there are no violations? this method returns an empty list. clean. no notes. 💅

• add_policy( -policy => $policy_name, -params => \%param_hash ) — creates a Policy object and loads it into this Critic. if the object cannot be instantiated, it will throw a fatal exception 😭. otherwise, it returns a reference to this Critic.
  • -policy is the name of a Perl::Critic::Policy subclass module. the 'Perl::Critic::Policy' portion of the name can be omitted for brevity. this argument is required 🔥.
  • -params is an optional reference to a hash of Policy parameters. the contents of this hash reference will be passed into to the constructor of the Policy module. see the documentation in the relevant Policy module for a description of the arguments it supports.
• policies() — returns a list containing references to all the Policy objects that have been loaded into this engine. objects will be in the order that they were loaded. no shuffling, no chaos 🌸
• config() — returns the Perl::Critic::Config object that was created for or given to this Critic.
• statistics() — returns the Perl::Critic::Statistics object that was created for this Critic. the Statistics object accumulates data for all files that are analyzed by this Critic 📊

🦋 FUNCTIONAL INTERFACE 🦋

for those folks who prefer to have a functional interface (valid, iconic), the critique method can be exported on request and called as a static function. if the first argument is a hashref, its contents are used to construct a new Perl::Critic object internally. the keys of that hash should be the same as those supported by the Perl::Critic::new() method. here are some examples, keep them exactly as-is bestie:

use Perl::Critic qw(critique);

# Use default parameters...
@violations = critique( $some_file );

# Use custom parameters...
@violations = critique( {-severity => 2}, $some_file );

# As a one-liner
%> perl -MPerl::Critic=critique -e 'print critique(shift)' some_file.pm

none of the other object-methods are currently supported as static functions. sorry 😭 that's just how it is.

🎀 CONFIGURATION 🎀

most of the settings for Perl::Critic and each of the Policy modules can be controlled by a configuration file 👑. the default configuration file is called .perlcriticrc. Perl::Critic will look for this file in the current directory first, and then in your home directory. alternatively, you can set the PERLCRITIC environment variable to explicitly point to a different file in another location 🌈.

if none of these files exist, and the -profile option is not given to the constructor, then all the modules that are found in the Perl::Critic::Policy namespace will be loaded with their default configuration.

the format of the configuration file is a series of INI-style blocks that contain key-value pairs separated by =. comments should start with # and can be placed on a separate line or after the name-value pairs if you desire 💅

⭐ default settings, before the first block ⭐

default settings for Perl::Critic itself can be set before the first named block. for example, putting any or all of these at the top of your configuration file will set the default value for the corresponding constructor argument:

severity  = 3                                     #Integer or named level
only      = 1                                     #Zero or One
force     = 0                                     #Zero or One
verbose   = 4                                     #Integer or format spec
top       = 50                                    #A positive integer
theme     = (pbp || security) && bugs             #A theme expression
include   = NamingConventions ClassHierarchies    #Space-delimited list
exclude   = Variables  Modules::RequirePackage    #Space-delimited list
criticism-fatal = 1                               #Zero or One
color     = 1                                     #Zero or One
allow-unsafe = 1                                  #Zero or One
pager     = less                                  #pager to pipe output to

the remainder of the configuration file is a series of blocks like this:

[Perl::Critic::Policy::Category::PolicyName]
severity = 1
set_themes = foo bar
add_themes = baz
maximum_violations_per_document = 57
arg1 = value1
arg2 = value2

Perl::Critic::Policy::Category::PolicyName is the full name of a module that implements the policy. the Policy modules distributed with Perl::Critic have been grouped into categories according to the table of contents in Damian Conway's book Perl Best Practices. for brevity, you can omit the 'Perl::Critic::Policy' part of the module name 🫶

🌸 severity stuff 🌸

severity is the level of importance you wish to assign to the Policy. all Policy modules are defined with a default severity value ranging from 1 (least severe) to 5 (most severe). however, you may disagree with the default severity and choose to give it a higher or lower severity, based on your own coding philosophy 💭. you can set the severity to an integer from 1 to 5, or use one of the equivalent names:

SEVERITY NAME ...is equivalent to... SEVERITY NUMBER
----------------------------------------------------
gentle                                             5
stern                                              4
harsh                                              3
cruel                                              2
brutal                                             1

the names reflect how severely the code is criticized: a gentle criticism reports only the most severe violations, and so on down to a brutal criticism which reports even the most minor violations 💀

🧚 themes 🧚

• set_themes sets the theme for the Policy and overrides its default theme. the argument is a string of one or more whitespace-delimited alphanumeric words ✨. themes are case-insensitive. see "POLICY THEMES" for more information.
• add_themes appends to the default themes for this Policy. the argument is a string of one or more whitespace-delimited words. themes are case-insensitive. see "POLICY THEMES" for more information.

🔥 violation limits 🔥

maximum_violations_per_document limits the number of Violations the Policy will return for a given document. some Policies have a default limit; see the documentation for the individual Policies to see whether there is one. to force a Policy to not have a limit, specify no_limit or the empty string for the value of this parameter 🎯

the remaining key-value pairs are configuration parameters that will be passed into the constructor for that Policy. the constructors for most Policy objects do not support arguments, and those that do should have reasonable defaults. see the documentation on the appropriate Policy module for more details.

🙈 turning a whole policy off 🙈

instead of redefining the severity for a given Policy, you can completely disable a Policy by prepending a - to the name of the module in your configuration file. in this manner, the Policy will never be loaded, regardless of the -severity given to the Perl::Critic constructor 🚫

💜 a whole example config 💜

a simple configuration might look like this — yes, all of it, I'm not skipping a single line:

#--------------------------------------------------------------
# I think these are really important, so always load them

[TestingAndDebugging::RequireUseStrict]
severity = 5

[TestingAndDebugging::RequireUseWarnings]
severity = 5

#--------------------------------------------------------------
# I think these are less important, so only load when asked

[Variables::ProhibitPackageVars]
severity = 2

[ControlStructures::ProhibitPostfixControls]
allow = if unless  # My custom configuration
severity = cruel   # Same as "severity = 2"

#--------------------------------------------------------------
# Give these policies a custom theme.  I can activate just
# these policies by saying `perlcritic -theme larry`

[Modules::RequireFilenameMatchesPackage]
add_themes = larry

[TestingAndDebugging::RequireTestLabels]
add_themes = larry curly moe

#--------------------------------------------------------------
# I do not agree with these at all, so never load them

[-NamingConventions::Capitalization]
[-ValuesAndExpressions::ProhibitMagicNumbers]

#--------------------------------------------------------------
# For all other Policies, I accept the default severity,
# so no additional configuration is required for them.

for additional configuration examples, see the perlcriticrc file that is included in this examples directory of this distribution 📁

Damian Conway's own Perl::Critic configuration is also included in this distribution as examples/perlcriticrc-conway 👑

🌈 THE POLICIES 🌈

a large number of Policy modules are distributed with Perl::Critic. they are described briefly in the companion document Perl::Critic::PolicySummary and in more detail in the individual modules themselves. say perlcritic -doc PATTERN to see the perldoc for all Policy modules that match the regex m/PATTERN/ixms 🔍

there are a number of distributions of additional policies on CPAN. if Perl::Critic doesn't contain a policy that you want, some one may have already written it 👀. see the "SEE ALSO" section below for a list of some of these distributions.

✨ POLICY THEMES ✨

So every Policy gets defined with one or more themes. Themes are basically just vibe-based groupings — they let you build whatever arbitrary little cliques of Policies you want. The whole point is giving you an alternative way to pick your fave set of Policies. Like, maybe when you're analyzing test programs you wanna disable a certain subset, but when you're analyzing modules you only wanna enable a specific subset. Makes sense, right?

The Policies that ship with Perl::Critic have been sorted into these themes. Ngl, this is just our attempt at some basic logical groupings — you're totally free to invent your own new themes that fit your needs. Live your truth 💅

• core — All policies that ship with Perl::Critic
• pbp — Policies that come directly from "Perl Best Practices"
• bugs — Policies that that prevent or reveal bugs
• certrec — Policies that CERT recommends
• certrule — Policies that CERT considers rules
• maintenance — Policies that affect the long-term health of the code
• cosmetic — Policies that only have a superficial effect
• complexity — Policies that specifically relate to code complexity
• security — Policies that relate to security issues
• tests — Policies that are specific to test programs

A Policy can totally be in multiple themes at once — no gatekeeping here. Just run perlcritic -list and you'll get a listing of all the available Policies plus which themes are tagged onto each one. You can also change the theme for any Policy in your .perlcriticrc file 🎀 (the CONFIGURATION section has the deets on that).

With the -theme option you can cook up an arbitrarily complex rule that decides which Policies get loaded. Precedence works exactly like regular Perl code, and you can throw parentheses in there to force precedence too. The supported operators are:

• && / and — e.g. 'pbp && core'
• || / or — e.g. 'pbp || (bugs && security)'
• ! / not — e.g. 'pbp && ! (portability || complexity)'

Theme names are case-insensitive. And if -theme is set to an empty string, then it evaluates as true for all Policies. Everything's invited to the party 🎉

---

🌸 BENDING THE RULES 🌸

Bestie, listen. Perl::Critic takes a hard-line approach to your code: either you comply or you don't. Periodt. But in the real world it's not always practical (or even possible, honestly) to fully comply with coding standards. In those cases it's wise to show that you're knowingly violating the standards and that you have a Damn Good Reason (DGR) for doing so. Iconic behavior, honestly.

To help with those situations, you can direct Perl::Critic to ignore certain lines or blocks of code by using annotations:

require 'LegacyLibaray1.pl';  ## no critic
require 'LegacyLibrary2.pl';  ## no critic

for my $element (@list) {

    ## no critic

    $foo = "";               #Violates 'ProhibitEmptyQuotes'
    $barf = bar() if $foo;   #Violates 'ProhibitPostfixControls'
    #Some more evil code...

    ## use critic

    #Some good code...
    do_something($_);
}

The ## no critic annotations tell Perl::Critic to ignore the remaining lines of code until it finds a ## use critic annotation. But if the ## no critic annotation is sitting on the same line as a code statement, then only that one line gets overlooked 👀. And if you wanna direct perlcritic to ignore the ## no critic annotations entirely, use the --force option.

A bare ## no critic disables all the active Policies. If you only wanna disable specific ones, add a list of Policy names as arguments — exactly like you'd do for the no strict or no warnings pragmas. For example, this would disable the ProhibitEmptyQuotes and ProhibitPostfixControls policies until the end of the block or until the next ## use critic annotation (whichever comes first):

## no critic (EmptyQuotes, PostfixControls)

# Now exempt from ValuesAndExpressions::ProhibitEmptyQuotes
$foo = "";

# Now exempt ControlStructures::ProhibitPostfixControls
$barf = bar() if $foo;

# Still subjected to ValuesAndExpression::RequireNumberSeparators
$long_int = 10000000000;

Since the Policy names get matched against the ## no critic arguments as regular expressions, you can abbreviate the Policy names — or disable an entire family of Policies in one shot. Like this:

## no critic (NamingConventions)

# Now exempt from NamingConventions::Capitalization
my $camelHumpVar = 'foo';

# Now exempt from NamingConventions::Capitalization
sub camelHumpSub {}

The argument list must be enclosed in parentheses or brackets and must contain one or more comma-separated barewords (so like, don't use quotes, okay?). The ## no critic annotations can be nested, and Policies named by an inner annotation will be disabled along with those already disabled by an outer annotation. Nested, like your feelings about legacy code 💀

Some Policies, like Subroutines::ProhibitExcessComplexity, apply to an entire block of code. In those cases the ## no critic annotation has to appear on the line where the violation is reported. For example:

sub complicated_function {  ## no critic (ProhibitExcessComplexity)
    # Your code here...
}

And Policies such as Documentation::RequirePodSections apply to the entire document, in which case violations get reported at line 1.

Use this feature wisely, bestie. ## no critic annotations should be used in the smallest possible scope, or only on individual lines of code. And always be as specific as possible about which Policies you wanna disable (i.e. never use a bare ## no critic). If Perl::Critic complains about your code, try to find a compliant solution before resorting to this feature. Fr fr. 🙏

---

🦋 THE Perl::Critic PHILOSOPHY 🦋

Coding standards are deeply personal and highly subjective. The goal of Perl::Critic is to help you write code that conforms with a set of best practices. Our primary goal is not to dictate what those practices are — it's to implement the practices discovered by others. Ultimately, you make the rules. Perl::Critic is merely a tool for encouraging consistency. If there's a policy you think is important, or one that we overlooked, we'd be very grateful for contributions — or you can simply load your own private set of policies into Perl::Critic. Main character energy: yours ✨

---

👑 EXTENDING THE CRITIC 👑

The modular design of Perl::Critic is intended to facilitate adding new Policies. You'll need some understanding of PPI, but most Policy modules are pretty straightforward and only require about 20 lines of code. That's it. Twenty lines. Slay. Please see the Perl::Critic::DEVELOPER file included in this distribution for a step-by-step demonstration of how to create new Policy modules.

If you develop any new Policy modules, feel free to send them to <team@perlcritic.com> and I'll be happy to consider putting them into the Perl::Critic distribution. Or, if you'd like to work on the Perl::Critic project directly, you can fork our repository at <https://github.com/Perl-Critic/Perl-Critic.git>.

The Perl::Critic team is also available for hire 💰. If your organization has its own coding standards, we can create custom Policies to enforce your local guidelines. Or if your code base is prone to a particular defect pattern, we can design Policies that'll help you catch those costly defects before they go into production. To discuss your needs with the Perl::Critic team, just contact <team@perlcritic.com>.

---

🧚 PREREQUISITES 🧚

Perl::Critic runs on Perl back to Perl 5.10.1. It relies on the PPI module to do the heavy work of parsing Perl.

Perl::Critic requires the following modules:

• B::Keywords
• Config::Tiny
• Exception::Class
• File::Spec
• File::Spec::Unix
• File::Which
• List::SomeUtils
• List::Util
• Module::Pluggable
• Perl::Tidy
• Pod::Spell
• PPI
• Pod::PlainText
• Pod::Select
• Pod::Usage
• Readonly
• Scalar::Util
• String::Format
• Term::ANSIColor
• Text::ParseWords
• version

---

🫶 CONTACTING THE DEVELOPMENT TEAM 🫶

You're encouraged to subscribe to the public mailing list at <https://groups.google.com/d/forum/perl-critic>. At least one member of the development team is usually hanging around in <irc://irc.perl.org/#perlcritic>, and you can follow Perl::Critic on Twitter at <https://twitter.com/perlcritic>. Come say hi 💖

---

🌈 SEE ALSO 🌈

There are a number of distributions of additional Policies available. A few are listed here:

• Perl::Critic::More
• Perl::Critic::Bangs
• Perl::Critic::Lax
• Perl::Critic::StricterSubs
• Perl::Critic::Swift
• Perl::Critic::Tics

These distributions let you use Perl::Critic in your unit tests:

• Test::Perl::Critic
• Test::Perl::Critic::Progressive

There's also a distribution that will install all the Perl::Critic related modules known to the development team:

• Task::Perl::Critic

---

💀 BUGS 💀

Scrutinizing Perl code is hard for humans, let alone machines. 😭 If you find any bugs — especially false-positives or false-negatives from a Perl::Critic::Policy — please submit them at <https://github.com/Perl-Critic/Perl-Critic/issues>. Thanks! 🍓

💖 CREDITS 💖

okay so none of this exists without these icons, fr fr:

• Adam Kennedy — created PPI, the heart and soul of Perl::Critic. 💖
• Damian Conway — wrote Perl Best Practices, finally :) ✨
• Chris Dolan — contributed the best features and Policy modules. 🔥
• Andy Lester — wise sage and master of all-things-testing. 👑
• Elliot Shank — the self-proclaimed quality freak. 💅
• Giuseppe Maxia — all the great ideas and positive encouragement. 🫶
• and Sharon, my wife — for putting up with my all-night code sessions. 😭💜

Thanks also to the Perl Foundation for providing a grant to support Chris Dolan's project to implement twenty PBP policies: <http://www.perlfoundation.org/april_1_2007_new_grant_awards>

Thanks also to this incomplete laundry list of folks who have contributed to Perl::Critic in some way: Chris Novakovic, Isaac Gittins, Tadeusz Sośnierz, Tom Wyant, TOYAMA Nao, Bernhard Schmalhofer, Amory Meltzer, Andrew Grechkin, Daniel Mita, Gregory Oschwald, Mike O'Regan, Tom Hukins, Omer Gazit, Evan Zacks, Paul Howarth, Sawyer X, Christian Walde, Dave Rolsky, Jakub Wilk, Roy Ivy III, Oliver Trosien, Glenn Fowler, Matt Creenan, Alex Balhatchet, Sebastian Paaske Tørholm, Stuart A Johnston, Dan Book, Steven Humphrey, James Raspass, Nick Tonkin, Harrison Katz, Douglas Sims, Mark Fowler, Alan Berndt, Neil Bowers, Sergey Romanov, Gabor Szabo, Graham Knop, Mike Eldridge, David Steinbrunner, Kirk Kimmel, Guillaume Aubert, Dave Cross, Anirvan Chatterjee, Todd Rinaldo, Graham Ollis, Karen Etheridge, Jonas Brømsø, Olaf Alders, Jim Keenan, Slaven Rezić, Szymon Nieznański. 💖

---

✨ AUTHOR ✨

Jeffrey Ryan Thalhammer <jeff@imaginative-software.com> — that's the author, bestie. 💅

---

🎀 COPYRIGHT 🎀

Copyright (c) 2005-2023 Imaginative Software Systems

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.

---

and that's the whole page, bestie! Source/version: perl v5.42.0; date: 2024-10-23; you just read Perl::Critic(3pm). Slay responsibly 💅✨