Reword the "threads still running" cleanup message.
[p5sagit/p5-mst-13.2.git] / ext / threads / threads.pm
CommitLineData
47ba8780 1package threads;
2
73e09c8f 3use 5.007_003;
47ba8780 4use strict;
5use warnings;
73e09c8f 6use Config;
7
8BEGIN {
9 unless ($Config{useithreads}) {
10 my @caller = caller(2);
11 die <<EOF;
12$caller[1] line $caller[2]:
13
14This Perl hasn't been configured and built properly for the threads
15module to work. (The 'useithreads' configuration option hasn't been used.)
16
17Having threads support requires all of Perl and all of the modules in
18the Perl installation to be rebuilt, it is not just a question of adding
19the threads module. (In other words, threaded and non-threaded Perls
20are binary incompatible.)
21
22If you want to the use the threads module, please contact the people
23who built your Perl.
24
25Cannot continue, aborting.
26EOF
27 }
28}
47ba8780 29
68795e93 30use overload
43d3ddbe 31 '==' => \&equal,
47ba8780 32 'fallback' => 1;
33
47ba8780 34#use threads::Shared;
35
dab065ea 36BEGIN {
37 warn "Warning, threads::shared has already been loaded. ".
38 "To enable shared variables for these modules 'use threads' ".
39 "must be called before any of those modules are loaded\n"
40 if($threads::shared::threads_shared);
41}
42
47ba8780 43require Exporter;
44require DynaLoader;
45
47ba8780 46our @ISA = qw(Exporter DynaLoader);
47
48our %EXPORT_TAGS = ( all => [qw()]);
49
50our @EXPORT_OK = ( @{ $EXPORT_TAGS{'all'} } );
51
52our @EXPORT = qw(
dcb6ccbc 53async
47ba8780 54);
678a9b6c 55our $VERSION = '0.99';
47ba8780 56
47ba8780 57
43d3ddbe 58sub equal {
47ba8780 59 return 1 if($_[0]->tid() == $_[1]->tid());
60 return 0;
61}
62
dcb6ccbc 63sub async (&;@) {
64 my $cref = shift;
65 return threads->new($cref,@_);
66}
67
8222d950 68$threads::threads = 1;
47ba8780 69
70bootstrap threads $VERSION;
71
68795e93 72# why document 'new' then use 'create' in the tests!
73*create = \&new;
74
47ba8780 75# Preloaded methods go here.
76
771;
78__END__
79
80=head1 NAME
81
82threads - Perl extension allowing use of interpreter based threads from perl
83
84=head1 SYNOPSIS
85
47ba8780 86use threads;
87
88sub start_thread {
89 print "Thread started\n";
90}
91
9c4972d9 92my $thread = threads->create("start_thread","argument");
47ba8780 93
9c4972d9 94$thread->create(sub { print "I am a thread"},"argument");
47ba8780 95
96$thread->join();
97
98$thread->detach();
99
100$thread = threads->self();
101
11c51ed3 102threads->tid();
103threads->self->tid();
104
105$thread->tid();
47ba8780 106
f9dff5f5 107threads->yield();
108
678a9b6c 109threads->list();
110
47ba8780 111=head1 DESCRIPTION
112
43d3ddbe 113Perl 5.6 introduced something called interpreter threads. Interpreter
114threads are different from "5005threads" (the thread model of Perl
1155.005) by creating a new perl interpreter per thread and not sharing
116any data or state between threads.
11c51ed3 117
43d3ddbe 118Prior to perl 5.8 this has only been available to people embedding
119perl and for emulating fork() on windows.
11c51ed3 120
43d3ddbe 121The threads API is loosely based on the old Thread.pm API. It is very
122important to note that variables are not shared between threads, all
123variables are per default thread local. To use shared variables one
124must use threads::shared.
11c51ed3 125
43d3ddbe 126It is also important to note that you preferably enable threads by
127doing C<use threads> as early as possible and that it is not possible
dab065ea 128to enable threading inside an eval ""; In particular, if you are
129intending to share variables with threads::shared, you must
130C<use threads> before you C<use threads::shared> and threads will emit
131a warning if you do it the other way around.
47ba8780 132
133=over
134
9c4972d9 135=item $thread = threads->create(function, LIST)
47ba8780 136
ad91d581 137This will create a new thread with the entry point function and give
138it LIST as parameters. It will return the corresponding threads
139object.
47ba8780 140
11c51ed3 141=item $thread->join
47ba8780 142
43d3ddbe 143This will wait for the corresponding thread to join. When it finishes
144join will return the return values of the entry point function. If a
678a9b6c 145thread has been detached, an error will be thrown..
47ba8780 146
11c51ed3 147=item $thread->detach
47ba8780 148
43d3ddbe 149Will throw away the return value from the thread and make it
150non-joinable.
47ba8780 151
152=item threads->self
153
154This will return the object for the current thread.
155
11c51ed3 156=item $thread->tid
47ba8780 157
678a9b6c 158This will return the id of the thread. threads->tid() is a quick way
159to get current thread id if you don't have your thread handy.
47ba8780 160
f9dff5f5 161=item threads->yield();
162
163This will tell the OS to let this thread yield CPU time to other threads.
f3278b06 164However this is highly depending on the underlying thread implementation.
f9dff5f5 165
678a9b6c 166=item threads->list();
167
168This will return a list of all non joined, non detached threads.
169
386c44e5 170=item async BLOCK;
171
172C<async> creates a thread to execute the block immediately following
173it. This block is treated as an anonymous sub, and so must have a
174semi-colon after the closing brace. Like C<threads-&gt;new>, C<async>
175returns a thread object.
176
47ba8780 177=back
178
e4f9f4fe 179=head1 WARNINGS
180
181=over 4
182
c133c03f 183=item A thread exited while %d other threads were still running
e4f9f4fe 184
c133c03f 185A thread (not necessarily the main thread) exited while there were
186still other threads running. Usually it's a good idea to first collect
187the return values of the created threads by joining them, and only then
188exit from then main thread.
e4f9f4fe 189
190=back
47ba8780 191
678a9b6c 192=head1 BUGS / TODO
193
194The current implmentation of threads has been an attempt to get
195a correct threading system working that could be built on,
196and optimized, in newer versions of perl.
197
198Current the overhead of creating a thread is rather large,
199also the cost of returning values can be large. These are areas
200were there most likely will be work done to optimize what data
201that needs to be cloned.
47ba8780 202
203=over
204
678a9b6c 205=item Parent-Child threads.
206
207On some platforms it might not be possible to destroy "parent"
208threads while there are still existing child "threads".
209
210This will be possibly be fixed in later versions of perl.
211
212=item tid is I32
213
214The tid is a 32 bit integer, it can potentially overflow.
215This might be fixed in a later version of perl.
47ba8780 216
678a9b6c 217=item Returning objects
47ba8780 218
678a9b6c 219When you return an object the entire stash that the object is blessed
220as well. This will lead to a large memory usage.
221The ideal situation would be to detect the original stash if it existed.
222
223=item PERL_OLD_SIGNALS are not threadsafe, will not be.
47ba8780 224
225=back
226
227=head1 AUTHOR and COPYRIGHT
228
11c51ed3 229Arthur Bergman E<lt>arthur at contiller.seE<gt>
47ba8780 230
43d3ddbe 231threads is released under the same license as Perl.
47ba8780 232
68795e93 233Thanks to
47ba8780 234
68795e93 235Richard Soderberg E<lt>rs at crystalflame.netE<gt>
ad91d581 236Helping me out tons, trying to find reasons for races and other weird bugs!
47ba8780 237
ad91d581 238Simon Cozens E<lt>simon at brecon.co.ukE<gt>
239Being there to answer zillions of annoying questions
47ba8780 240
ad91d581 241Rocco Caputo E<lt>troc at netrus.netE<gt>
47ba8780 242
ad91d581 243Vipul Ved Prakash E<lt>mail at vipul.netE<gt>
47ba8780 244Helping with debugging.
245
246please join perl-ithreads@perl.org for more information
247
b5807cdb 248
11c51ed3 249
47ba8780 250
251=head1 SEE ALSO
252
11c51ed3 253L<perl>, L<threads::shared>, L<perlcall>, L<perlembed>, L<perlguts>
47ba8780 254
255=cut