diff options
| author | Jerry D. Hedden <jdhedden@cpan.org> | 2007-09-05 05:50:24 -0400 |
|---|---|---|
| committer | Rafael Garcia-Suarez <rgarciasuarez@gmail.com> | 2007-09-05 13:53:16 +0000 |
| commit | 7c8caac01fed14372509c397e3e7b8ddc0ce3513 (patch) | |
| tree | 63c9d993a7714d5da142008bc751848560c47c1e /ext/threads/shared/shared.pm | |
| parent | 01112dae7d0bba7f093e86dca1adee26f9da1b1c (diff) | |
| download | perl-7c8caac01fed14372509c397e3e7b8ddc0ce3513.tar.gz | |
threads::shared 1.13
From: "Jerry D. Hedden" <jdhedden@cpan.org>
Message-ID: <1ff86f510709050650j3c3f54b2o64c8ce05dc4c8604@mail.gmail.com>
p4raw-id: //depot/perl@31795
Diffstat (limited to 'ext/threads/shared/shared.pm')
| -rw-r--r-- | ext/threads/shared/shared.pm | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/ext/threads/shared/shared.pm b/ext/threads/shared/shared.pm index fe8cf6e5d2..06829a1409 100644 --- a/ext/threads/shared/shared.pm +++ b/ext/threads/shared/shared.pm @@ -5,7 +5,7 @@ use 5.008; use strict; use warnings; -our $VERSION = '1.12'; +our $VERSION = '1.13'; my $XS_VERSION = $VERSION; $VERSION = eval $VERSION; @@ -73,7 +73,7 @@ threads::shared - Perl extension for sharing data structures between threads =head1 VERSION -This document describes threads::shared version 1.12 +This document describes threads::shared version 1.13 =head1 SYNOPSIS @@ -108,7 +108,7 @@ This document describes threads::shared version 1.12 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 +to share variables across different threads (and pseudo-forks on Win32). It is used together with the L<threads> module. =head1 EXPORT @@ -205,11 +205,11 @@ the variable, and blocks until another thread does a C<cond_signal> or C<cond_broadcast> for that same locked variable. The variable that C<cond_wait> blocked on is relocked after the C<cond_wait> is satisfied. If there are multiple threads C<cond_wait>ing on the same variable, all but one -will reblock waiting to reacquire the lock on the variable. (So if you're only +will re-block waiting to reacquire the lock on the variable. (So if you're only using C<cond_wait> 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. +re-locking the variable are not. In its second form, C<cond_wait> takes a shared, B<unlocked> variable followed by a shared, B<locked> variable. The second variable is unlocked and thread @@ -368,7 +368,7 @@ L<threads::shared> Discussion Forum on CPAN: L<http://www.cpanforum.com/dist/threads-shared> Annotated POD for L<threads::shared>: -L<http://annocpan.org/~JDHEDDEN/threads-shared-1.12/shared.pm> +L<http://annocpan.org/~JDHEDDEN/threads-shared-1.13/shared.pm> Source repository: L<http://code.google.com/p/threads-shared/> |