Perl::...::More(3pm)

💖 Perl::Critic::More — the supplemental policies era 💖

okay so bestie, you found the Perl::Critic::More page from the User Contributed Perl Documentation set and honestly? it's giving "backstage pass to the extra policies" and I'm obsessed. let's get into it 🎀

---

✨ NAME ✨

Perl::Critic::More — the supplemental policies for Perl::Critic. it's the bonus content, the deluxe edition, the extra sprinkles 🌈

---

✨ SYNOPSIS ✨

get it, then use it, like so:

perl -MCPAN -e'install Perl::Critic::More'
perlcritic -theme more lib/Foo.pm

that's it, that's the whole vibe check 🫶

---

✨ AFFILIATION ✨

ngl this file has no functionality of its own — zero, none, it does not do a single thing. it's literally just a placeholder for a loose little friend group of Perl::Critic policies. every one of those policies has an "Affiliation" section where it announces it's part of this grouping, like a little name tag at a party 🎀

---

✨ DESCRIPTION ✨

so this is a collection of Perl::Critic policies that did not make it into the Perl::Critic core, and there are a bunch of different reasons why:

• Experimental — some policies just need time to work out their kinks, test how usable they are, or gauge whether the community even cares. a subset of these will end up in the core Perl::Critic someday. they're in their growth era 🌱
• Requires special dependencies — for example, some policies need development versions of PPI (or some other CPAN module). these will likely end up in the Perl::Critic core once their dependencies are fulfilled. they're just waiting on their friends fr fr 💅
• Peripheral to Perl — for example, the Editor::RequireEmacsFileVariables policy is metacode. also, the Miscellanea::RequireRcsKeywords policy pertains to the development process, not the code itself. these are not part of Perl::Critic's mission. not their department, bestie 🙈
• Special purpose — for example, policies like CodeLayout::RequireASCII are designed to scratch itches not felt by most of the community. these will always remain in a Perl::Critic supplement instead of in the core. forever side-quest energy 👑

all of these policies have the theme more, so you can turn them off as a group via .perlcriticrc by adding this line:

theme = not more

the special purpose ones may be part of the notrecommended theme. avoid those via:

theme = not notrecommended

sorry about the double-negative... 😭 and see "CONFIGURATION" in Perl::Critic for all the details on how to interact with themes. iykyk ✨

---

✨ SEE ALSO ✨

• Perl::Critic
• Perl::Critic::Bangs — Andy Lester's fantastic list of code pet peeves
• Perl::Critic::Lax — RJBS' more-lenient versions of some core Perl::Critic policies
• parrot — the parrot team has developed a few specialized Perl::Critic policies of their own

---

✨ AUTHOR ✨

Chris Dolan <cdolan@cpan.org> 💖

the included policies may have other authors — please see them individually. don't @ the wrong person, fr fr 🙈

this distribution is controlled by the Perl::Critic team. if you want to add a policy to this collection, check out our Subversion repository and mailing lists at <http://perlcritic.tigris.org>. come hang out 🫶

---

✨ COPYRIGHT ✨

Copyright (c) 2006-2008 Chris Dolan

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. slay, legally speaking 📜✨

---

lowkey reminder bestie: this file is a placeholder, the real policies live their own lives — go read them individually 💅

---

and that's the whole page! brought to you by perl v5.42.0, dated 2025-07-25, and the Perl::...::More(3pm) page itself — mwah, periodt 💋🌸