Change 30151 by [EMAIL PROTECTED] on 2007/02/06 22:35:29
Upgrade to threads::shared 1.07 (doc tweaks)
Affected files ...
... //depot/perl/ext/threads/shared/Changes#4 edit
... //depot/perl/ext/threads/shared/README#5 edit
... //depot/perl/ext/threads/shared/shared.pm#45 edit
Differences ...
==== //depot/perl/ext/threads/shared/Changes#4 (text) ====
Index: perl/ext/threads/shared/Changes
--- perl/ext/threads/shared/Changes#3~29599~ 2006-12-19 20:20:14.000000000
-0800
+++ perl/ext/threads/shared/Changes 2007-02-06 14:35:29.000000000 -0800
@@ -1,6 +1,9 @@
Revision history for Perl extension threads::shared.
-1.06 Tue Dec 19 13:26:46 EST 2006
+1.07 - Mon Feb 5 15:41:50 EST 2007
+ - POD tweaks per Wolfgang Laun
+
+1.06 Wed Dec 20 14:01:57 EST 2006
- Fixed a bug in unlocking code
- Added stress test for cond_* functions
==== //depot/perl/ext/threads/shared/README#5 (text) ====
Index: perl/ext/threads/shared/README
--- perl/ext/threads/shared/README#4~29599~ 2006-12-19 20:20:14.000000000
-0800
+++ perl/ext/threads/shared/README 2007-02-06 14:35:29.000000000 -0800
@@ -1,4 +1,4 @@
-threads::shared version 1.06
+threads::shared version 1.07
============================
This module needs Perl 5.8.0 or later compiled with USEITHREADS.
==== //depot/perl/ext/threads/shared/shared.pm#45 (text) ====
Index: perl/ext/threads/shared/shared.pm
--- perl/ext/threads/shared/shared.pm#44~29599~ 2006-12-19 20:20:14.000000000
-0800
+++ perl/ext/threads/shared/shared.pm 2007-02-06 14:35:29.000000000 -0800
@@ -5,7 +5,7 @@
use strict;
use warnings;
-our $VERSION = '1.06';
+our $VERSION = '1.07';
my $XS_VERSION = $VERSION;
$VERSION = eval $VERSION;
@@ -73,7 +73,7 @@
=head1 VERSION
-This document describes threads::shared version 1.06
+This document describes threads::shared version 1.07
=head1 SYNOPSIS
@@ -170,16 +170,16 @@
C<lock> places a lock on a variable until the lock goes out of scope. If the
variable is locked by another thread, the C<lock> call will block until it's
-available. C<lock> is recursive, so multiple calls to C<lock> 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<lock @a>,
-any other thread doing a C<lock($a[12])> won't block.
+available. Multiple calls to C<lock> by the same thread from within
+dynamically nested scopes are safe -- the variable will remain locked until
+the outermost lock on the variable goes out of scope.
+
+Locking a container object, such as a hash or array, doesn't lock the elements
+of that container. For example, if a thread does a C<lock(@a)>, any other
+thread doing a C<lock($a[12])> won't block.
-C<lock> will traverse up references exactly I<one> level. C<lock(\$a)> is
-equivalent to C<lock($a)>, while C<lock(\\$a)> is not.
+C<lock()> follows references exactly I<one> level. C<lock(\$a)> is equivalent
+to C<lock($a)>, while C<lock(\\$a)> is not.
Note that you cannot explicitly unlock a variable; you can only wait for the
lock to go out of scope. This is most easily accomplished by locking the
@@ -277,7 +277,7 @@
=head1 OBJECTS
L<threads::shared> exports a version of L<bless()|perlfunc/"bless REF"> that
-works on shared objects such that i<blessings> propagate across threads.
+works on shared objects such that I<blessings> propagate across threads.
# Create a shared 'foo' object
my $foo;
@@ -342,11 +342,11 @@
and scalar refs are not affected by this problem.)
It is often not wise to share an object unless the class itself has been
-written to support sharing. For example, an object's destructor may get called
-multiple times, one for each thread's scope exit. Another example, is that
-the contents of hash-based objects will be lost due to the above mentioned
-limitation. See F<examples/class.pl> (in the CPAN distribution of this
-module) for how to create a class that supports object sharing.
+written to support sharing. For example, an object's destructor may get
+called multiple times, once for each thread's scope exit. Another danger is
+that the contents of hash-based objects will be lost due to the above
+mentioned limitation. See F<examples/class.pl> (in the CPAN distribution of
+this module) for how to create a class that supports object sharing.
Does not support C<splice> on arrays!
@@ -368,7 +368,7 @@
L<http://www.cpanforum.com/dist/threads-shared>
Annotated POD for L<threads::shared>:
-L<http://annocpan.org/~JDHEDDEN/threads-shared-1.06/shared.pm>
+L<http://annocpan.org/~JDHEDDEN/threads-shared-1.07/shared.pm>
L<threads>, L<perlthrtut>
End of Patch.
