summaryrefslogtreecommitdiff
path: root/dist/threads-shared
diff options
context:
space:
mode:
authorjdhedden <jdhedden@cpan.org>2017-02-26 13:24:12 -0500
committerJames E Keenan <jkeenan@cpan.org>2017-02-26 15:56:49 -0500
commite04fc787e1e33df064cc27d6711be40de8cab63f (patch)
tree41df2a06a6e2aff16e29a01cdc5608113c94fabd /dist/threads-shared
parentbce4a2abeb8652d19e97d3bf07dd2580a3cc2e6c (diff)
downloadperl-e04fc787e1e33df064cc27d6711be40de8cab63f.tar.gz
Upgrade to threads::shared 1.55
Diffstat (limited to 'dist/threads-shared')
-rw-r--r--dist/threads-shared/lib/threads/shared.pm18
1 files changed, 10 insertions, 8 deletions
diff --git a/dist/threads-shared/lib/threads/shared.pm b/dist/threads-shared/lib/threads/shared.pm
index d42981b86b..5a203b0cd7 100644
--- a/dist/threads-shared/lib/threads/shared.pm
+++ b/dist/threads-shared/lib/threads/shared.pm
@@ -7,7 +7,7 @@ use warnings;
use Scalar::Util qw(reftype refaddr blessed);
-our $VERSION = '1.54'; # Please update the pod, too.
+our $VERSION = '1.55'; # Please update the pod, too.
my $XS_VERSION = $VERSION;
$VERSION = eval $VERSION;
@@ -195,7 +195,7 @@ threads::shared - Perl extension for sharing data structures between threads
=head1 VERSION
-This document describes threads::shared version 1.54
+This document describes threads::shared version 1.55
=head1 SYNOPSIS
@@ -570,16 +570,18 @@ not propagate the blessing to the shared reference:
Therefore, you should bless objects before sharing them.
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, 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.
+written to support sharing. For example, a shared object's destructor may
+get called multiple times, once for each thread's scope exit, or may not
+get called at all if it is embedded inside another shared object. Another
+issue 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.
Destructors may not be called on objects if those objects still exist at
global destruction time. If the destructors must be called, make sure
there are no circular references and that nothing is referencing the
-objects, before the program ends.
+objects before the program ends.
Does not support C<splice> on arrays. Does not support explicitly changing
array lengths via $#array -- use C<push> and C<pop> instead.