Benchmark-Harness 1.09
- Released by
- GLENNWOOD
- Version
- Release Date
- 2004-11-05
- Kwalitee
- 137.5
- Core Kwalitee
- 96.88
- LINKS
Benchmark-Harness 1.09
Kwalitee Issues
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: Benchmark-Harness-1.09/Harness/Trace.pm -- Around line 84: Unknown directive: =item1 Around line 88: Unknown directive: =item1 Around line 98: Unknown directive: =item1 Around line 146: Unknown directive: =item1 Benchmark-Harness-1.09/Harness/TraceHighRes.pm -- Around line 136: Unknown directive: =item1 Around line 140: Unknown directive: =item1 Benchmark-Harness-1.09/Harness.pm -- Around line 83: Unknown directive: =item2 Around line 88: Unknown directive: =item2 Around line 94: Unknown directive: =item2
- meta_yml_declares_perl_version
-
If you are using Build.PL define the {requires}{perl} = VERSION field. If you are using MakeMaker (Makefile.PL) you should upgrade ExtUtils::MakeMaker to 6.48 and use MIN_PERL_VERSION parameter. Perl::MinimumVersion can help you determine which version of Perl your module needs.
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- has_tests_in_t_dir
-
Add tests or move tests.pl to the t/ directory!
- meta_yml_has_license
-
Define the license if you are using in Build.PL. If you are using MakeMaker (Makefile.PL) you should upgrade to ExtUtils::MakeMaker version 6.31.
- use_warnings
-
Add 'use warnings' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.
Error: Benchmark::Harness, Benchmark::Harness::Handler, Benchmark::Harness::Trace, Benchmark::Harness::TraceHighRes
- consistent_version
-
Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade).
Error: 1.01,1.09
- meta_yml_has_provides
-
Add all modules contained in this distribution to the META.yml field 'provides'. Module::Build or Dist::Zilla::Plugin::MetaProvides do this automatically for you.
- meta_yml_has_repository_resource
-
Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).
- has_separate_license_file
-
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.