diff options
author | David Steinbrunner <dsteinbrunner@pobox.com> | 2013-05-21 07:01:50 -0400 |
---|---|---|
committer | James E Keenan <jkeenan@cpan.org> | 2013-05-25 04:46:27 +0200 |
commit | 1a471f9e757c3f621b4b066b68334e6706e0c3b9 (patch) | |
tree | 8b4f48e80d78cf504f4942a650e51b339009e59b /lib/Thread.pm | |
parent | c0b435603334620c1f3cdd7aedc09f29b4f07381 (diff) | |
download | perl-1a471f9e757c3f621b4b066b68334e6706e0c3b9.tar.gz |
typo fix for Thread
Bump $VERSION.
Diffstat (limited to 'lib/Thread.pm')
-rw-r--r-- | lib/Thread.pm | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/Thread.pm b/lib/Thread.pm index 247f90ccc9..395b7ebc71 100644 --- a/lib/Thread.pm +++ b/lib/Thread.pm @@ -4,7 +4,7 @@ use strict; use warnings; no warnings 'redefine'; -our $VERSION = '3.02'; +our $VERSION = '3.03'; $VERSION = eval $VERSION; BEGIN { @@ -168,7 +168,7 @@ 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 reaquire the lock on the variable. (So if you're only using +to require the lock on the variable. (So if you're only using C<cond_wait> for synchronization, give up the lock as soon as possible.) |