X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=ext%2Fthreads%2Fthreads.pm;h=dcd2aa015c9a65619b9fa687f4feb3ff04fdde7c;hb=8043fdafce9b64db18484779a548e4f4adefc5ed;hp=6ad724e0a2a5894b2155573c461c73dbf256c35b;hpb=32419a4c4b0d4e513a7ca9f706bbde8c03c40c61;p=p5sagit%2Fp5-mst-13.2.git diff --git a/ext/threads/threads.pm b/ext/threads/threads.pm index 6ad724e..dcd2aa0 100755 --- a/ext/threads/threads.pm +++ b/ext/threads/threads.pm @@ -31,8 +31,6 @@ use overload '==' => \&equal, 'fallback' => 1; -#use threads::Shared; - BEGIN { warn "Warning, threads::shared has already been loaded. ". "To enable shared variables for these modules 'use threads' ". @@ -52,17 +50,22 @@ our @EXPORT_OK = ( @{ $EXPORT_TAGS{'all'} } ); our @EXPORT = qw( async ); -our $VERSION = '0.99'; +our $VERSION = '1.05'; -sub equal { - return 1 if($_[0]->tid() == $_[1]->tid()); - return 0; -} +# || 0 to ensure compatibility with previous versions +sub equal { ($_[0]->tid == $_[1]->tid) || 0 } -sub async (&;@) { - my $cref = shift; - return threads->new($cref,@_); +# use "goto" trick to avoid pad problems from 5.8.1 (fixed in 5.8.2) +# should also be faster +sub async (&;@) { unshift @_,'threads'; goto &new } + +sub object { + return undef unless @_ > 1; + foreach (threads->list) { + return $_ if $_->tid == $_[1]; + } + return undef; } $threads::threads = 1; @@ -97,6 +100,7 @@ threads - Perl extension allowing use of interpreter based threads from perl $thread->detach(); $thread = threads->self(); + $thread = threads->object( $tid ); $thread->tid(); threads->tid(); @@ -121,12 +125,13 @@ important to note that variables are not shared between threads, all variables are per default thread local. To use shared variables one must use threads::shared. -It is also important to note that you must enable threads by -doing C as early as possible and that it is not possible -to enable threading inside an eval ""; In particular, if you are -intending to share variables with threads::shared, you must -C before you C and threads will emit -a warning if you do it the other way around. +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 possible to enable threading inside an C, C, +C, or C. In particular, if you are intending to share +variables with threads::shared, you must C before you +C and C will emit a warning if you do +it the other way around. =over @@ -134,18 +139,26 @@ a warning if you do it the other way around. This will create a new thread with the entry point function and give it LIST as parameters. It will return the corresponding threads -object. The new() method is an alias for create(). +object, or C if thread creation failed. The new() method is an +alias for create(). =item $thread->join This will wait for the corresponding thread to join. When the thread finishes, join() will return the return values of the entry point function. If the thread has been detached, an error will be thrown. + +The context (scalar or list) of the thread creation is also the +context for join(). This means that if you intend to return an array +from a thread, you must use Cnew(...)>, and +that if you intend to return a scalar, you must use C. + If the program exits without all other threads having been either joined or detached, then a warning will be issued. (A program exits either because one of its threads explicitly calls exit(), or in the case of the main thread, reaches the end of the main program file.) + =item $thread->detach Will make the thread unjoinable, and cause any eventual return value @@ -166,6 +179,12 @@ new thread that's created. NB the class method C<< threads->tid() >> is a quick way to get the current thread id if you don't have your thread object handy. +=item threads->object( tid ) + +This will return the thread object for the thread associated with the +specified tid. Returns undef if there is no thread associated with the tid +or no tid is specified or the specified tid is undef. + =item threads->yield(); This is a suggestion to the OS to let this thread yield CPU time to other @@ -201,7 +220,7 @@ exit from the main thread. =back -=head1 BUGS / TODO +=head1 TODO The current implementation of threads has been an attempt to get a correct threading system working that could be built on, @@ -212,6 +231,8 @@ also the cost of returning values can be large. These are areas were there most likely will be work done to optimize what data that needs to be cloned. +=head1 BUGS + =over =item Parent-Child threads. @@ -219,8 +240,8 @@ that needs to be cloned. On some platforms it might not be possible to destroy "parent" threads while there are still existing child "threads". -This will be possibly be fixed in later versions of perl. - +This will possibly be fixed in later versions of perl. + =item tid is I32 The thread id is a 32 bit integer, it can potentially overflow. @@ -232,19 +253,30 @@ When you return an object the entire stash that the object is blessed as well. This will lead to a large memory usage. The ideal situation would be to detect the original stash if it existed. +=item Creating threads inside BEGIN blocks + +Creating threads inside BEGIN blocks (or during the compilation phase +in general) does not work. (In Windows, trying to use fork() inside +BEGIN blocks is an equally losing proposition, since it has been +implemented in very much the same way as threads.) + =item PERL_OLD_SIGNALS are not threadsafe, will not be. +If your Perl has been built with PERL_OLD_SIGNALS (one has +to explicitly add that symbol to ccflags, see C), +signal handling is not threadsafe. + =back =head1 AUTHOR and COPYRIGHT -Arthur Bergman Earthur at contiller.seE +Arthur Bergman Esky at nanisky.comE threads is released under the same license as Perl. Thanks to -Richard Soderberg Ers at crystalflame.netE +Richard Soderberg Eperl at crystalflame.netE Helping me out tons, trying to find reasons for races and other weird bugs! Simon Cozens Esimon at brecon.co.ukE