package threads::shared; use 5.008; use strict; use warnings; BEGIN { require Exporter; our @ISA = qw(Exporter); our @EXPORT = qw(share cond_wait cond_timedwait cond_broadcast cond_signal); our $VERSION = '0.93'; if ($threads::threads) { *cond_wait = \&cond_wait_enabled; *cond_timedwait = \&cond_timedwait_enabled; *cond_signal = \&cond_signal_enabled; *cond_broadcast = \&cond_broadcast_enabled; require XSLoader; XSLoader::load('threads::shared',$VERSION); push @EXPORT,'bless'; } else { # String eval is generally evil, but we don't want these subs to exist at all # if threads are loaded successfully. Vivifying them conditionally this way # saves on average about 4K of memory per thread. eval <<'EOD'; sub cond_wait (\[$@%];\[$@%]) { undef } sub cond_timedwait (\[$@%]$;\[$@%]) { undef } sub cond_signal (\[$@%]) { undef } sub cond_broadcast (\[$@%]) { undef } sub share (\[$@%]) { return $_[0] } EOD } } $threads::shared::threads_shared = 1; sub threads::shared::tie::SPLICE { die "Splice not implemented for shared arrays"; } __END__ =head1 NAME threads::shared - Perl extension for sharing data structures between threads =head1 SYNOPSIS use threads; use threads::shared; my $var : shared; my($scalar, @array, %hash); share($scalar); share(@array); share(%hash); my $bar = &share([]); $hash{bar} = &share({}); { lock(%hash); ... } cond_wait($scalar); cond_timedwait($scalar, time() + 30); cond_broadcast(@array); cond_signal(%hash); my $lockvar : shared; # condition var != lock var cond_wait($var, $lockvar); cond_timedwait($var, time()+30, $lockvar); =head1 DESCRIPTION By default, variables are private to each thread, and each newly created thread gets a private copy of each existing variable. This module allows you to share variables across different threads (and pseudoforks on Win32). It is used together with the threads module. =head1 EXPORT C, C, C, C, C Note that if this module is imported when C has not yet been loaded, then these functions all become no-ops. This makes it possible to write modules that will work in both threaded and non-threaded environments. =head1 FUNCTIONS =over 4 =item share VARIABLE C takes a value and marks it as shared. You can share a scalar, array, hash, scalar ref, array ref or hash ref. C will return the shared rvalue but always as a reference. C will traverse up references exactly I level. C is equivalent to C, while C is not. A variable can also be marked as shared at compile time by using the C attribute: C. If you want to share a newly created reference unfortunately you need to use C<&share([])> and C<&share({})> syntax due to problems with Perl's prototyping. =item lock VARIABLE C places a lock on a variable until the lock goes out of scope. If the variable is locked by another thread, the C call will block until it's available. C is recursive, so multiple calls to C are safe -- the variable will remain locked until the outermost lock on the variable goes out of scope. If a container object, such as a hash or array, is locked, all the elements of that container are not locked. For example, if a thread does a C, any other thread doing a C won't block. C will traverse up references exactly I level. C is equivalent to C, while C is not. Note that you cannot explicitly unlock a variable; you can only wait for the lock to go out of scope. If you need more fine-grained control, see L. =item cond_wait VARIABLE =item cond_wait CONDVAR, LOCKVAR The C function takes a B variable as a parameter, unlocks the variable, and blocks until another thread does a C or C for that same locked variable. The variable that C blocked on is relocked after the C is satisfied. If there are multiple threads Cing on the same variable, all but one will reblock waiting to reacquire the lock on the variable. (So if you're only using C for synchronisation, give up the lock as soon as possible). The two actions of unlocking the variable and entering the blocked wait state are atomic, the two actions of exiting from the blocked wait state and relocking the variable are not. In its second form, C takes a shared, B variable followed by a shared, B variable. The second variable is unlocked and thread execution suspended until another thread signals the first variable. It is important to note that the variable can be notified even if no thread C or C on the variable. It is therefore important to check the value of the variable and go back to waiting if the requirement is not fulfilled. For example, to pause until a shared counter drops to zero: { lock($counter); cond_wait($count) until $counter == 0; } =item cond_timedwait VARIABLE, ABS_TIMEOUT =item cond_timedwait CONDVAR, ABS_TIMEOUT, LOCKVAR In its two-argument form, C takes a B variable and an absolute timeout as parameters, unlocks the variable, and blocks until the timeout is reached or another thread signals the variable. A false value is returned if the timeout is reached, and a true value otherwise. In either case, the variable is re-locked upon return. Like C, this function may take a shared, B variable as an additional parameter; in this case the first parameter is an B condition variable protected by a distinct lock variable. Again like C, waking up and reacquiring the lock are not atomic, and you should always check your desired condition after this function returns. Since the timeout is an absolute value, however, it does not have to be recalculated with each pass: lock($var); my $abs = time() + 15; until ($ok = desired_condition($var)) { last if !cond_timedwait($var, $abs); } # we got it if $ok, otherwise we timed out! =item cond_signal VARIABLE The C function takes a B variable as a parameter and unblocks one thread that's Cing on that variable. If more than one thread is blocked in a C on that variable, only one (and which one is indeterminate) will be unblocked. If there are no threads blocked in a C on the variable, the signal is discarded. By always locking before signaling, you can (with care), avoid signaling before another thread has entered cond_wait(). C will normally generate a warning if you attempt to use it on an unlocked variable. On the rare occasions where doing this may be sensible, you can skip the warning with { no warnings 'threads'; cond_signal($foo) } =item cond_broadcast VARIABLE The C function works similarly to C. C, though, will unblock B the threads that are blocked in a C on the locked variable, rather than only one. =back =head1 NOTES threads::shared is designed to disable itself silently if threads are not available. If you want access to threads, you must C before you C. threads will emit a warning if you use it after threads::shared. =head1 BUGS C is not supported on shared references. In the current version, C will only bless the thread local reference and the blessing will not propagate to the other threads. This is expected to be implemented in a future version of Perl. Does not support splice on arrays! Taking references to the elements of shared arrays and hashes does not autovivify the elements, and neither does slicing a shared array/hash over non-existent indices/keys autovivify the elements. share() allows you to C<< share $hashref->{key} >> without giving any error message. But the C<< $hashref->{key} >> is B shared, causing the error "locking can only be used on shared values" to occur when you attempt to C<< lock $hasref->{key} >>. =head1 AUTHOR Arthur Bergman Earthur at contiller.seE threads::shared is released under the same license as Perl Documentation borrowed from the old Thread.pm =head1 SEE ALSO L, L, L =cut