| Name : perl-criticism
| |
| Version : 1.20.0
| Vendor : (none)
|
| Release : 10pclos2017
| Date : 2017-07-13 06:41:43
|
| Group : Development/Perl
| Source RPM : perl-criticism-1.20.0-10pclos2017.src.rpm
|
| Size : 0.04 MB
| |
| Packager : bb2 < bb2>
| |
| Summary : Perl pragma to enforce coding standards and best-practices
|
Description :
This pragma enforces coding standards and promotes best-practices by
running your file through Perl::Critic before every execution. In a
production system, this usually isn\'t feasible because it adds a lot of
overhead at start-up. If you have a separate development environment, you
can effectively bypass the \'criticism\' pragma by not installing
Perl::Critic in the production environment. If Perl::Critic can\'t be
loaded, then \'criticism\' just fails silently.
Alternatively, the \'perlcritic\' command-line (which is distributed with
Perl::Critic) can be used to analyze your files on-demand and has some
additional configuration features. And Test::Perl::Critic provides a nice
interface for analyzing files during the build process.
If you\'d like to try Perl::Critic without installing anything, there is a
web-service available at the http://perlcritic.com manpage. 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. You can also invoke the perlcritic web-service from the command line
by doing an HTTP-post, such as one of these:
|
RPM found in directory: /vol/rzm3/linux-pclinuxos/pclinuxos/apt/pclinuxos/64bit/RPMS.x86_64 |
