X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=ext%2Fthreads%2Fthreads.pm;h=6bf15d04d491faaadb6de53d1b1ddbe71a23a694;hb=5e137bc214f9c21ed33df8110b67005fb915c4e7;hp=bec14b6e6381e1f64bb04a6ccb6cb7e807f5866f;hpb=69a9b4b8cb205b3194738b7a08fc3fb9f858174f;p=p5sagit%2Fp5-mst-13.2.git diff --git a/ext/threads/threads.pm b/ext/threads/threads.pm index bec14b6..6bf15d0 100755 --- a/ext/threads/threads.pm +++ b/ext/threads/threads.pm @@ -5,31 +5,27 @@ use 5.008; use strict; use warnings; -our $VERSION = '1.37'; +our $VERSION = '1.71'; my $XS_VERSION = $VERSION; $VERSION = eval $VERSION; +# Verify this Perl supports threads +require Config; +if (! $Config::Config{useithreads}) { + die("This Perl not built to support threads\n"); +} -BEGIN { - # Verify this Perl supports threads - use Config; - if (! $Config{useithreads}) { - die("This Perl not built to support threads\n"); - } - - # Declare that we have been loaded - $threads::threads = 1; - - # Complain if 'threads' is loaded after 'threads::shared' - if ($threads::shared::threads_shared) { - warn <<'_MSG_'; +# Complain if 'threads' is loaded after 'threads::shared' +if ($threads::shared::threads_shared) { + warn <<'_MSG_'; Warning, threads::shared has already been loaded. To enable shared variables, 'use threads' must be called before threads::shared or any module that uses it. _MSG_ - } } +# Declare that we have been loaded +$threads::threads = 1; # Load the XS code require XSLoader; @@ -47,18 +43,27 @@ sub import # Handle args while (my $sym = shift) { - if ($sym =~ /^stack/i) { - threads->set_stack_size(shift); - - } elsif ($sym =~ /^exit/i) { - my $flag = shift; - $threads::thread_exit_only = $flag =~ /^thread/i; - - } elsif ($sym =~ /all/) { + if ($sym =~ /^(?:stack|exit)/i) { + if (defined(my $arg = shift)) { + if ($sym =~ /^stack/i) { + threads->set_stack_size($arg); + } else { + $threads::thread_exit_only = $arg =~ /^thread/i; + } + } else { + require Carp; + Carp::croak("threads: Missing argument for option: $sym"); + } + + } elsif ($sym =~ /^str/i) { + import overload ('""' => \&tid); + + } elsif ($sym =~ /^(?::all|yield)$/) { push(@EXPORT, qw(yield)); } else { - push(@EXPORT, $sym); + require Carp; + Carp::croak("threads: Unknown import option: $sym"); } } @@ -89,7 +94,7 @@ sub exit # Class method only if (ref($class)) { require Carp; - Carp::croak("Usage: threads->exit(status)"); + Carp::croak('Usage: threads->exit(status)'); } $class->set_thread_exit_only(1); @@ -129,23 +134,29 @@ threads - Perl interpreter-based threads =head1 VERSION -This document describes threads version 1.37 +This document describes threads version 1.71 =head1 SYNOPSIS - use threads ('yield', 'stack_size' => 64*4096, 'exit' => 'threads_only'); + use threads ('yield', + 'stack_size' => 64*4096, + 'exit' => 'threads_only', + 'stringify'); sub start_thread { my @args = @_; print('Thread started: ', join(' ', @args), "\n"); } - my $thread = threads->create('start_thread', 'argument'); - $thread->join(); + my $thr = threads->create('start_thread', 'argument'); + $thr->join(); threads->create(sub { print("I am a thread\n"); })->join(); - my $thread3 = async { foreach (@files) { ... } }; - $thread3->join(); + my $thr2 = async { foreach (@files) { ... } }; + $thr2->join(); + if (my $err = $thr2->error()) { + warn("Thread error: $err\n"); + } # Invoke thread in list context (implicit) so it can return a list my ($thr) = threads->create(sub { return (qw/a b c/); }); @@ -154,16 +165,16 @@ This document describes threads version 1.37 sub { return (qw/a b c/); }); my @results = $thr->join(); - $thread->detach(); + $thr->detach(); # Get a thread's object - $thread = threads->self(); - $thread = threads->object($tid); + $thr = threads->self(); + $thr = threads->object($tid); # Get a thread's ID $tid = threads->tid(); - $tid = threads->self->tid(); - $tid = $thread->tid(); + $tid = $thr->tid(); + $tid = "$thr"; # Give other threads a chance to run threads->yield(); @@ -220,8 +231,11 @@ for emulating fork() on Windows. The I API is loosely based on the old Thread.pm API. It is very important to note that variables are not shared between threads, all variables -are by default thread local. To use shared variables one must use -L. +are by default thread local. To use shared variables one must also use +L: + + use threads; + use threads::shared; It is also important to note that you must enable threads by doing C as early as possible in the script itself, and that it is not @@ -323,6 +337,17 @@ thread in a program being 0, and incrementing by 1 for every thread created. Class method that allows a thread to obtain its own ID. +=item "$thr" + +If you add the C import option to your C declaration, +then using a threads object in a string or a string context (e.g., as a hash +key) will cause its ID to be used as the value: + + use threads qw(stringify); + + my $thr = threads->create(...); + print("Thread $thr started...\n"); # Prints out: Thread 1 started... + =item threads->object($tid) This will return the I object for the I thread associated @@ -352,7 +377,7 @@ list of all non-joined, non-detached I objects. In a scalar context, returns a count of the same. With a I argument (using C), returns a list of all -non-detached I objects that are still running. +non-joined, non-detached I objects that are still running. With a I argument (using C), returns a list of all non-joined, non-detached I objects that have finished running (i.e., @@ -377,9 +402,15 @@ to the more natural forms: C creates a thread to execute the block immediately following it. This block is treated as an anonymous subroutine, and so must have a -semi-colon after the closing brace. Like Ccreate()>, C +semicolon after the closing brace. Like Ccreate()>, C returns a I object. +=item $thr->error() + +Threads are executed in an C context. This method will return C +if the thread terminates I. Otherwise, it returns the value of +C<$@> associated with the thread's execution status in its C context. + =item $thr->_handle() This I method returns the memory location of the internal thread @@ -438,10 +469,10 @@ strongly discouraged. If C really is needed, then consider using the following: - threads->exit() if $threads::threads; # Thread friendly + threads->exit() if threads->can('exit'); # Thread friendly exit(status); -=item use threads 'exit' => 'thread_only' +=item use threads 'exit' => 'threads_only' This globally overrides the default behavior of calling C inside a thread, and effectively causes such calls to behave the same as @@ -461,16 +492,15 @@ thread only. =item $thr->set_thread_exit_only(boolean) This can be used to change the I behavior for a thread after -it has been created. With a I argument, C will cause the only -the thread to exit. With a I argument, C will terminate the +it has been created. With a I argument, C will cause only the +thread to exit. With a I argument, C will terminate the application. The I
thread is unaffected by this call. =item threads->set_thread_exit_only(boolean) -Class method for use inside a thread to changes its own behavior for -C. +Class method for use inside a thread to change its own behavior for C. The I
thread is unaffected by this call. @@ -486,13 +516,13 @@ thread. =item $thr->is_running() Returns true if a thread is still running (i.e., if its entry point function -has not yet finished/exited). +has not yet finished or exited). =item $thr->is_joinable() Returns true if the thread has finished running, is not detached and has not -yet been joined. In other works, the thread is ready to be joined and will -not I. +yet been joined. In other words, the thread is ready to be joined, and a call +to C<$thr-Ejoin()> will not I. =item $thr->is_detached() @@ -517,7 +547,7 @@ the appropriate type to be returned from C<-Ejoin()>. Because thread creation and thread joining may occur in different contexts, it may be desirable to state the context explicitly to the thread's entry point -function. This may be done by calling C<-Ecreate()> with a parameter hash +function. This may be done by calling C<-Ecreate()> with a hash reference as the first argument: my $thr = threads->create({'context' => 'list'}, \&foo); @@ -526,15 +556,17 @@ as the first argument: In the above, the threads object is returned to the parent thread in scalar context, and the thread's entry point function C will be called in list -context such that the parent thread can receive a list from the C<-Ejoin()> -call. Similarly, if you need the threads object, but your thread will not be +(array) context such that the parent thread can receive a list (array) from +the C<-Ejoin()> call. (C<'array'> is synonymous with C<'list'>.) + +Similarly, if you need the threads object, but your thread will not be returning a value (i.e., I context), you would do the following: my $thr = threads->create({'context' => 'void'}, \&foo); ... $thr->join(); -The context type may also be used as the I in the parameter hash followed +The context type may also be used as the I in the hash reference followed by a I value: threads->create({'scalar' => 1}, \&foo); @@ -563,8 +595,9 @@ L. =head2 threads->wantarray() -Class method to return the current thread's context. This is the same as -running L in the current thread. +Class method to return the current thread's context. This returns the same +value as running L inside the current +thread's entry point function. =head1 THREAD STACK SIZE @@ -578,9 +611,9 @@ By tuning the stack size to more accurately reflect your application's needs, you may significantly reduce your application's memory usage, and increase the number of simultaneously running threads. -N.B., on Windows, Address space allocation granularity is 64 KB, therefore, -setting the stack smaller than that on Win32 Perl will not save any more -memory. +Note that on Windows, address space allocation granularity is 64 KB, +therefore, setting the stack smaller than that on Win32 Perl will not save any +more memory. =over @@ -633,8 +666,8 @@ threaded applications. =item threads->create({'stack_size' => VALUE}, FUNCTION, ARGS) -The stack size an individual threads may also be specified. This may be done -by calling C<-Ecreate()> with a parameter hash as the first argument: +To specify a particular stack size for any individual thread, call +C<-Ecreate()> with a hash reference as the first argument: my $thr = threads->create({'stack_size' => 32*4096}, \&foo, @args); @@ -711,7 +744,7 @@ and I capabilities: ... } - # Create a semaphore and send it to a thread + # Create a semaphore and pass it to a thread my $sema = Thread::Semaphore->new(); my $thr = threads->create('thr_func', $sema); @@ -763,7 +796,8 @@ cause for the failure. =item Thread # terminated abnormally: ... A thread terminated in some manner other than just returning from its entry -point function. For example, the thread may have terminated using C. +point function, or by using Cexit()>. For example, the thread +may have terminated because of an error, or by using C. =item Using minimum thread stack size of # @@ -817,10 +851,71 @@ specified signal being used in a C<-Ekill()> call. =back -=head1 BUGS +=head1 BUGS AND LIMITATIONS + +Before you consider posting a bug report, please consult, and possibly post a +message to the discussion forum to see if what you've encountered is a known +problem. =over +=item Thread-safe modules + +See L when creating modules that may +be used in threaded applications, especially if those modules use non-Perl +data, or XS code. + +=item Using non-thread-safe modules + +Unfortunately, you may encounter Perl modules that are not I. +For example, they may crash the Perl interpreter during execution, or may dump +core on termination. Depending on the module and the requirements of your +application, it may be possible to work around such difficulties. + +If the module will only be used inside a thread, you can try loading the +module from inside the thread entry point function using C (and +C if needed): + + sub thr_func + { + require Unsafe::Module + # Unsafe::Module->import(...); + + .... + } + +If the module is needed inside the I
thread, try modifying your +application so that the module is loaded (again using C and +C<-Eimport()>) after any threads are started, and in such a way that no +other threads are started afterwards. + +If the above does not work, or is not adequate for your application, then file +a bug report on L against the problematic module. + +=item Current working directory + +On all platforms except MSWin32, the setting for the current working directory +is shared among all threads such that changing it in one thread (e.g., using +C) will affect all the threads in the application. + +On MSWin32, each thread maintains its own the current working directory +setting. + +=item Environment variables + +Currently, on all platforms except MSWin32, all I calls (e.g., using +C or back-ticks) made from threads use the environment variable +settings from the I
thread. In other words, changes made to C<%ENV> in +a thread will not be visible in I calls made by that thread. + +To work around this, set environment variables as part of the I call. +For example: + + my $msg = 'hello'; + system("FOO=$msg; echo \$FOO"); # Outputs 'hello' to STDOUT + +On MSWin32, each thread maintains its own set of environment variables. + =item Parent-child threads On some platforms, it might not be possible to destroy I threads while @@ -845,7 +940,7 @@ signalling behavior is only in effect in the following situations: =over 4 -=item * Perl was been built with C (see C). +=item * Perl has been built with C (see C). =item * The environment variable C is set to C (see L). @@ -863,17 +958,46 @@ Perl version and the application code, results may range from success, to (apparently harmless) warnings of leaked scalar, or all the way up to crashing of the Perl interpreter. +=item Returning objects from threads + +Returning objects from threads does not work. Depending on the classes +involved, you may be able to work around this by returning a serialized +version of the object (e.g., using L or L), and then +reconstituting it in the joining thread. If you're using Perl 5.10.0 or +later, and if the class supports L, +you can pass them via L. + +=item END blocks in threads + +It is possible to add L to threads by using L or +L with the appropriate code. These C blocks +will then be executed when the thread's interpreter is destroyed (i.e., either +during a C<-Ejoin()> call, or at program termination). + +However, calling any L methods in such an C block will most +likely I (e.g., the application may hang, or generate an error) due to +mutexes that are needed to control functionality within the L module. + +For this reason, the use of C blocks in threads is B +discouraged. + =item Perl Bugs and the CPAN Version of L -Support for threads extents beyond the code in this module (i.e., -F and F), and into the Perl iterpreter itself. Older +Support for threads extends beyond the code in this module (i.e., +F and F), and into the Perl interpreter itself. Older versions of Perl contain bugs that may manifest themselves despite using the latest version of L from CPAN. There is no workaround for this other -than upgrading to the lastest version of Perl. +than upgrading to the latest version of Perl. -(Before you consider posting a bug report, please consult, and possibly post a -message to the discussion forum to see if what you've encountered is a known -problem.) +Even with the latest version of Perl, it is known that certain constructs +with threads may result in warning messages concerning leaked scalars or +unreferenced scalars. However, such warnings are harmless, and may safely be +ignored. + +You can search for L related bug reports at +L. If needed submit any new bugs, problems, +patches, etc. to: L =back @@ -887,7 +1011,10 @@ L Discussion Forum on CPAN: L Annotated POD for L: -L +L + +Source repository: +L L, L @@ -904,10 +1031,12 @@ L Artur Bergman Esky AT crucially DOT netE -threads is released under the same license as Perl. - CPAN version produced by Jerry D. Hedden +=head1 LICENSE + +threads is released under the same license as Perl. + =head1 ACKNOWLEDGEMENTS Richard Soderberg Eperl AT crystalflame DOT netE -