Coro 0.9 Deleted
Kwalitee Issues
- has_license_in_source_file
-
Add =head1 LICENSE and the text of the license to the main module in your code.
- use_strict
-
Add 'use strict' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules are strictly written.
Error: Coro, Coro::Channel, Coro::Cont, Coro::Event, Coro::Handle, Coro::MakeMaker, Coro::RWLock, Coro::Select, Coro::Semaphore, Coro::SemaphoreSet, Coro::Signal, Coro::Socket, Coro::Specific, Coro::State, Coro::Timer, Coro::Util
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: Coro-0.9/Coro/Cont.pm -- Around line 16: Non-ASCII character seen before =encoding in 'grün'. Assuming UTF-8 Coro-0.9/Coro.pm -- Around line 342: Nested L<> are illegal. Pretending inner one is X<...> so can continue looking for other errors. Coro-0.9/Event/Event.pm -- Around line 196: You forgot a '=back' before '=head1' Coro-0.9/Event/Handle.pm -- Around line 376: You forgot a '=back' before '=head1' Coro-0.9/Event/Util.pm -- Around line 86: You forgot a '=back' before '=head1'
- 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.
- 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.
- has_known_license_in_source_file
-
Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.
- 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: Coro, Coro::Channel, Coro::Cont, Coro::Event, Coro::Handle, Coro::MakeMaker, Coro::RWLock, Coro::Select, Coro::Semaphore, Coro::SemaphoreSet, Coro::Signal, Coro::Socket, Coro::Specific, Coro::State, Coro::Timer, Coro::Util
- 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).
Modules
Name | Abstract | Version | View |
---|---|---|---|
Coro | coroutine process abstraction | 0.9 | metacpan |
Coro::Channel | message queues | 0.9 | metacpan |
Coro::Cont | schmorp's faked continuations | 0.9 | metacpan |
Coro::Event | do events the coro-way | 0.9 | metacpan |
Coro::Handle | non-blocking io with a blocking interface. | 0.9 | metacpan |
Coro::MakeMaker | MakeMaker glue for the C-level Coro API | metacpan | |
Coro::RWLock | reader/write locks | 0.9 | metacpan |
Coro::Select | a (slow but event-aware) replacement for CORE::select | 0.9 | metacpan |
Coro::Semaphore | non-binary semaphores | 0.9 | metacpan |
Coro::SemaphoreSet | hash of semaphores. | 0.9 | metacpan |
Coro::Signal | coroutine signals (binary semaphores) | 0.9 | metacpan |
Coro::Socket | non-blocking socket-io | 0.9 | metacpan |
Coro::Specific | manage coroutone-specific variables. | 0.9 | metacpan |
Coro::State | create and manage simple coroutines | 0.9 | metacpan |
Coro::Timer | simple timer package, independent of used event loops | 0.9 | metacpan |
Coro::Util | various utility functions. | 0.9 | metacpan |