Search results for "module:Perl::Critic::Policy::Documentation::RequirePodAtEnd"
Perl::Critic::Policy::Documentation::RequirePodAtEnd - All POD should be after __END__.
Perl stops processing code when it sees an "__END__" statement. So, to save processing time, it's faster to put documentation after the "__END__". Also, writing all the POD in one place usually leads to a more cohesive document, rather than being for...
PETDANCE/Perl-Critic-1.152 - 17 Oct 2023 04:09:08 UTC
Perl::Critic::Policy::Documentation::RequireFinalCut - end POD with =cut directive
This policy is part of the "Perl::Critic::Pulp" add-on. It asks you to end POD with a "=cut" directive at the end of a file. =head1 DOCO Some text. =cut # ok The idea is to have a definite end indication for human readers. Perl and the POD processors...
KRYDE/Perl-Critic-Pulp-99 - 28 Feb 2021 08:34:14 UTC
Perl::Critic::Policy::Documentation::RequireEndBeforeLastPod - require __END__ before POD at end of file
This policy is part of the "Perl::Critic::Pulp" add-on. It requires that you put an "__END__" before POD which is at the end of a file. For example, program_code(); 1; __END__ # good =head1 NAME ... and not merely program_code(); 1; # bad =head1 NAME...
KRYDE/Perl-Critic-Pulp-99 - 28 Feb 2021 08:34:14 UTC