diff options
| author | Father Chrysostomos <sprout@cpan.org> | 2013-11-01 12:49:25 -0700 |
|---|---|---|
| committer | Father Chrysostomos <sprout@cpan.org> | 2013-11-01 12:49:25 -0700 |
| commit | 7fb64fce3b0ff424c9217398ce4492f8cca015c1 (patch) | |
| tree | 9e5008ab039349210285f20e365a6fe115e22eaa /dist/threads-shared | |
| parent | eb588b415de1f3dc82397114d294e082bfd0230d (diff) | |
| download | perl-7fb64fce3b0ff424c9217398ce4492f8cca015c1.tar.gz | |
threads::shared: Remove redundant description just added
In commit fd013656aac I moved the documentation for the two warnings
that threads::shared produces from perldiag.pod to shared.pm, without
rewording anything.
These two warnings had almost identical descriptions, and--I found
later--basically repeat some of the documentation of the cond_signal
function, so point to that description in the warnings section and
avoid repeating things.
Diffstat (limited to 'dist/threads-shared')
| -rw-r--r-- | dist/threads-shared/lib/threads/shared.pm | 22 |
1 files changed, 1 insertions, 21 deletions
diff --git a/dist/threads-shared/lib/threads/shared.pm b/dist/threads-shared/lib/threads/shared.pm index 1e0bbd9796..a4b77a8a88 100644 --- a/dist/threads-shared/lib/threads/shared.pm +++ b/dist/threads-shared/lib/threads/shared.pm @@ -527,32 +527,12 @@ L<threads::shared>. =item cond_broadcast() called on unlocked variable -Within a thread-enabled program, you tried to call cond_broadcast() on a -variable which wasn't locked. The cond_broadcast() function is used to -wake up another thread that is waiting in a cond_wait(). To ensure that -the signal isn't sent before the other thread has a chance to enter the -wait, it is usual for the signaling thread first to wait for a lock on -variable. This lock attempt will only succeed after the other thread has -entered cond_wait() and thus relinquished the lock. - =item cond_signal() called on unlocked variable -Within a thread-enabled program, you tried to call cond_signal() on a -variable which wasn't locked. The cond_signal() function is used to wake -up another thread that is waiting in a cond_wait(). To ensure that the -signal isn't sent before the other thread has a chance to enter the wait, -it is usual for the signaling thread first to wait for a lock on variable. -This lock attempt will only succeed after the other thread has entered -cond_wait() and thus relinquished the lock. +See L</"cond_signal VARIABLE">, above. =back -If needed, thread warnings can be suppressed by using: - - no warnings 'threads'; - -in the appropriate scope. - =head1 BUGS AND LIMITATIONS When C<share> is used on arrays, hashes, array refs or hash refs, any data |