Perl-Critic-TooMuchCode
perlcritic add-ons that generally check for dead code. (by gugod)
Perl-Critic
The leading static analyzer for Perl. Configurable, extensible, powerful. (by Perl-Critic)
| Perl-Critic-TooMuchCode | Perl-Critic | |
|---|---|---|
| 2 | 2 | |
| 7 | 173 | |
| - | 0.0% | |
| 5.5 | 5.8 | |
| about 1 month ago | about 2 months ago | |
| Perl | Perl | |
| GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Perl-Critic-TooMuchCode
Posts with mentions or reviews of Perl-Critic-TooMuchCode.
We have used some of these posts to build our list of alternatives
and similar projects.
-
CPAN Release of TooMuchCode 0.18
It's just about a week after the release of 0.17 and after asynchronously exchanged some thoughts with @oalders and @ferki (Issue #25), I decide to make a follow-up release shortly.
-
CPAN installation as a test, with GitHub workflow
This workflow is currently used in Perl-Critic-TooMuchCode, with a few runs already finished here.
Perl-Critic
Posts with mentions or reviews of Perl-Critic.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-05-24.
-
Everyone’s a (Perl) critic, and you can be too!
The perlcritic tool is often your first defense against “awkward, hard to read, error-prone, or unconventional constructs in your code,” per its description. It’s part of a class of programs historically known as linters, so-called because like a clothes dryer machine’s lint trap, they “detect small errors with big effects.” (Another such linter is perltidy, which I’ve referenced in the past.)
-
First public release of Perl::Critic policy: *::ProhibitHighPrecedentLogicalOperatorErrorHandling
I gathered that at least the release of this policy would benefit somebody, since Nathan had proposed changes and another user had commented on my PR. So instead of laying dormant in a PR queue I could just release the policies as stand-alone policies.
What are some alternatives?
When comparing Perl-Critic-TooMuchCode and Perl-Critic you can also consider the following projects:
perl-critic-policy-inputoutput-prohibithighprecedentlogicaloperatorerrorhandling - Perl::Critic policy, prohibiting logical error handling in open statements
Rsnapshot - a tool for backing up your data using rsync (if you want to get help, use https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss)
mojo - :sparkles: Mojolicious - Perl real-time web framework
postgresqltuner - Simple script to analyse your PostgreSQL database configuration, and give tuning advice
mojo - The Mojo Programming Language