1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
|
package Perl::Critic::Policy::Community::Threads;
use strict;
use warnings;
use Perl::Critic::Utils qw(:severities :classification :ppi);
use parent 'Perl::Critic::Policy';
our $VERSION = 'v1.0.4';
use constant DESC => 'Using interpreter threads';
use constant EXPL => 'Interpreter threads are discouraged, they are not lightweight and fast as other threads may be. Try an event loop, forks.pm, or Parallel::Prefork.';
sub supported_parameters { () }
sub default_severity { $SEVERITY_MEDIUM }
sub default_themes { 'community' }
sub applies_to { 'PPI::Statement::Include' }
sub violates {
my ($self, $elem) = @_;
return $self->violation(DESC, EXPL, $elem) if $elem->pragma eq 'threads';
return ();
}
1;
=head1 NAME
Perl::Critic::Policy::Community::Threads - Interpreter-based threads are
officially discouraged
=head1 DESCRIPTION
Perl interpreter L<threads> are officially discouraged. They were created to
emulate C<fork()> in Windows environments, and are not fast or lightweight as
one may expect. Non-blocking code or I/O can be easily parallelized by using an
event loop such as L<POE>, L<IO::Async>, or L<Mojo::IOLoop>. Blocking code is
usually better parallelized by forking, which on Unix-like systems is fast and
efficient. Modules such as L<forks> and L<Parallel::Prefork> can make forking
easier to work with, as well as forking modules for event loops such as
L<POE::Wheel::Run>, L<IO::Async::Process>, or L<Mojo::IOLoop/"subprocess">.
=head1 AFFILIATION
This policy is part of L<Perl::Critic::Community>.
=head1 CONFIGURATION
This policy is not configurable except for the standard options.
=head1 AUTHOR
Dan Book, C<dbook@cpan.org>
=head1 COPYRIGHT AND LICENSE
Copyright 2015, Dan Book.
This library is free software; you may redistribute it and/or modify it under
the terms of the Artistic License version 2.0.
=head1 SEE ALSO
L<Perl::Critic>
|
