ParseLex 2.03
- Released by
- PVERD
- Version
- Release Date
- 1998-11-03
- Kwalitee
- 131.25
- Core Kwalitee
- 84.38
- LINKS
ParseLex 2.03 Deleted
Kwalitee Issues
- has_meta_yml
-
Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.
- has_changelog
-
Add a Changelog (best named 'Changes') to the distribution. It should list at least major changes implemented in newer versions.
- buildtool_not_executable
-
Change the permissions of Build.PL/Makefile.PL to not-executable.
- main_module_version_matches_dist_version
-
Make sure that the main module name and version are the same of the distribution.
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: ParseLex-2.03/doc/Lex.fr.pod -- Around line 3: Non-ASCII character seen before =encoding in 'Générateur'. Assuming CP1252 ParseLex-2.03/doc/Token.fr.pod -- Around line 3: Non-ASCII character seen before =encoding in 'définissant'. Assuming CP1252 Around line 235: You forgot a '=back' before '=head1' ParseLex-2.03/doc/Token.pod -- Around line 228: You forgot a '=back' before '=head1'
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- 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: Parse::ALex, Parse::CLex, Parse::Lex, Parse::Template, Parse::Token, Parse::Token-t, Parse::Trace, Parse::YYLex
- consistent_version
-
Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade).
Error: 0.02,0.91,2.03
- has_separate_license_file
-
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
- has_security_doc
-
Add SECURITY(.pod|md). See Software::Security::Policy.
- security_doc_contains_contact
-
Add SECURITY(.pod|md) and add a contact address. See Software::Security::Policy.
- has_contributing_doc
-
Add CONTRIBUTING(.pod|md). See https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.