It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Find sources: "Perl::Critic" – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Perl::Critic|concern=Non-notable module}} ~~~~Timestamp: 20090524220749 22:07, 24 May 2009 (UTC) Administrators: delete |
Perl::Critic is a perl module and tool designed to help perl programmers ensure that their code complies with commonly held best practices for perl programming. Since it is a static code analysis tool, it does not actually execute the code that it examines.
History
The Perl::Critic project grew out of a desire to have an automated tool to help enforce the coding standards recommended by the Perl Best Practices book by Damian Conway. Historically, analyzing perl code statically had proven to be difficult because the only tool available to parse Perl code was the perl program itself, which executed the code. The PPI tool was developed to parse, analyze and manipulate Perl code without actually executing it. By using this tool, the Perl::Critic module could be developed to find code that did not comply with the coding standards recommended by the book. It was eventually expanded to find violations of many policies not originally found in the book.
Resources
- The Perl::Critic page at CPAN
- perlcritic.com will run Perl::Critic over your source code
 | This software article is a stub. You can help Wikipedia by expanding it. |