fix 17425 for VMS
[p5sagit/p5-mst-13.2.git] / ext / threads / shared / shared.pm
CommitLineData
b050c948 1package threads::shared;
73e09c8f 2
3use 5.007_003;
b050c948 4use strict;
5use warnings;
73e09c8f 6
a446a88f 7require Exporter;
8our @ISA = qw(Exporter);
81f1a921 9our @EXPORT = qw(share cond_wait cond_broadcast cond_signal _refcnt _id _thrcnt);
a446a88f 10our $VERSION = '0.90';
11
caf25f3b 12if ($threads::threads) {
6f942b98 13 *cond_wait = \&cond_wait_enabled;
14 *cond_signal = \&cond_signal_enabled;
15 *cond_broadcast = \&cond_broadcast_enabled;
9c4972d9 16 require XSLoader;
17 XSLoader::load('threads::shared',$VERSION);
18}
19else {
a6b94e59 20 *share = \&share_disabled;
21 *cond_wait = \&cond_wait_disabled;
22 *cond_signal = \&cond_signal_disabled;
dab065ea 23 *cond_broadcast = \&cond_broadcast_disabled;
b050c948 24}
25
b050c948 26
b050c948 27sub cond_wait_disabled { return @_ };
28sub cond_signal_disabled { return @_};
29sub cond_broadcast_disabled { return @_};
b050c948 30sub share_disabled { return @_}
31
dab065ea 32$threads::shared::threads_shared = 1;
33
6b85e4fe 34
35sub threads::shared::tie::SPLICE
36{
37 die "Splice not implemented for shared arrays";
38}
39
b050c948 40__END__
41
42=head1 NAME
43
44threads::shared - Perl extension for sharing data structures between threads
45
46=head1 SYNOPSIS
47
73e09c8f 48 use threads;
b050c948 49 use threads::shared;
50
38875929 51 my $var : shared;
52
4cab98c0 53 my($scalar, @array, %hash);
54 share($scalar);
55 share(@array);
aaf3876d 56 share(%hash);
caf25f3b 57 my $bar = &share([]);
58 $hash{bar} = &share({});
b050c948 59
38875929 60 { lock(%hash); ... }
61
b050c948 62 cond_wait($scalar);
515f0976 63 cond_broadcast(@array);
64 cond_signal(%hash);
b050c948 65
66=head1 DESCRIPTION
67
38875929 68By default, variables are private to each thread, and each newly created
69thread gets a private copy of each existing variable. This module allows
70you to share variables across different threads (and pseudoforks on
71win32). It is used together with the threads module.
b050c948 72
515f0976 73=head1 EXPORT
b050c948 74
38875929 75C<share>, C<lock>, C<cond_wait>, C<cond_signal>, C<cond_broadcast>
515f0976 76
77=head1 FUNCTIONS
78
79=over 4
80
81=item share VARIABLE
82
4cab98c0 83C<share> takes a value and marks it as shared. You can share a scalar, array,
84hash, scalar ref, array ref or hash ref. C<share> will return the shared value.
515f0976 85
86C<share> will traverse up references exactly I<one> level.
87C<share(\$a)> is equivalent to C<share($a)>, while C<share(\\$a)> is not.
88
38875929 89A variable can also be marked as shared at compile time by using the
90C<shared> attribute: C<my $var : shared>.
91
caf25f3b 92If you want to share a newly created reference, unfourtunetly you need to use
93C<&share([])> and C<&share({})> syntax due to problems with perls prototyping.
94
515f0976 95=item lock VARIABLE
96
97C<lock> places a lock on a variable until the lock goes out of scope. If
98the variable is locked by another thread, the C<lock> call will block until
99it's available. C<lock> is recursive, so multiple calls to C<lock> are
4cab98c0 100safe -- the variable will remain locked until the outermost lock on the
38875929 101variable goes out of scope.
515f0976 102
103If a container object, such as a hash or array, is locked, all the elements
104of that container are not locked. For example, if a thread does a C<lock
105@a>, any other thread doing a C<lock($a[12])> won't block.
106
107C<lock> will traverse up references exactly I<one> level.
108C<lock(\$a)> is equivalent to C<lock($a)>, while C<lock(\\$a)> is not.
109
38875929 110Note that you cannot explicitly unlock a variable; you can only wait for
111the lock to go out of scope. If you need more fine-grained control, see
112L<threads::shared::semaphore>.
515f0976 113
114=item cond_wait VARIABLE
115
116The C<cond_wait> function takes a B<locked> variable as a parameter,
117unlocks the variable, and blocks until another thread does a C<cond_signal>
118or C<cond_broadcast> for that same locked variable. The variable that
119C<cond_wait> blocked on is relocked after the C<cond_wait> is satisfied.
120If there are multiple threads C<cond_wait>ing on the same variable, all but
4cab98c0 121one will reblock waiting to reacquire the lock on the variable. (So if
38875929 122you're only using C<cond_wait> for synchronisation, give up the lock as
123soon as possible). The two actions of unlocking the variable and entering
124the blocked wait state are atomic, The two actions of exiting from the
125blocked wait state and relocking the variable are not.
515f0976 126
127It is important to note that the variable can be notified even if no
128thread C<cond_signal> or C<cond_broadcast> on the variable. It is therefore
129important to check the value of the variable and go back to waiting if the
4cab98c0 130requirement is not fulfilled.
515f0976 131
132=item cond_signal VARIABLE
133
134The C<cond_signal> function takes a B<locked> variable as a parameter and
135unblocks one thread that's C<cond_wait>ing on that variable. If more than
136one thread is blocked in a C<cond_wait> on that variable, only one (and
137which one is indeterminate) will be unblocked.
138
139If there are no threads blocked in a C<cond_wait> on the variable, the
38875929 140signal is discarded. By always locking before signaling, you can (with
141care), avoid signaling before another thread has entered cond_wait().
142
143C<cond_signal> will normally generate a warning if you attempt to use it
144on an unlocked variable. On the rare occasions where doing this may be
145sensible, you can skip the warning with
146
147 { no warnings 'threads'; cond_signal($foo) }
515f0976 148
149=item cond_broadcast VARIABLE
150
151The C<cond_broadcast> function works similarly to C<cond_signal>.
152C<cond_broadcast>, though, will unblock B<all> the threads that are blocked
153in a C<cond_wait> on the locked variable, rather than only one.
b050c948 154
4cab98c0 155=back
dab065ea 156
157=head1 NOTES
158
8c5dce87 159threads::shared is designed to disable itself silently if threads are
dab065ea 160not available. If you want access to threads, you must C<use threads>
161before you C<use threads::shared>. threads will emit a warning if you
8c5dce87 162use it after threads::shared.
dab065ea 163
b050c948 164=head1 BUGS
165
4cab98c0 166C<bless> is not supported on shared references. In the current version,
515f0976 167C<bless> will only bless the thread local reference and the blessing
4cab98c0 168will not propagate to the other threads. This is expected to be
169implemented in a future version of Perl.
515f0976 170
b050c948 171Does not support splice on arrays!
b050c948 172
58122748 173Taking references to the elements of shared arrays and hashes does not
174autovivify the elements, and neither does slicing a shared array/hash
175over non-existent indices/keys autovivify the elements.
176
b050c948 177=head1 AUTHOR
178
aaf3876d 179Arthur Bergman E<lt>arthur at contiller.seE<gt>
b050c948 180
aaf3876d 181threads::shared is released under the same license as Perl
b050c948 182
5e549d84 183Documentation borrowed from the old Thread.pm
515f0976 184
b050c948 185=head1 SEE ALSO
186
5e549d84 187L<threads>, L<perlthrtut>, L<http://www.perl.com/pub/a/2002/06/11/threads.html>
b050c948 188
189=cut