threads::shared: Don’t link to moving targets

The Scalar::Util documentation has changed, so the links are broken.
But we cannot just update the link targets, as threads::shared is
living a double life and may be installed along with an older
Scalar::Util.

1 files changed, 4 insertions, 4 deletions

diff --git a/dist/threads-shared/lib/threads/shared.pm b/dist/threads-shared/lib/threads/shared.pm
index 5a24a9840c..1337b58ad9 100644
--- a/dist/threads-shared/lib/threads/shared.pm
+++ b/dist/threads-shared/lib/threads/shared.pm
@@ -336,7 +336,7 @@ then the C<undef> substitution will be performed silently.
 
 C<is_shared> checks if the specified variable is shared or not.  If shared,
 returns the variable's internal ID (similar to
-L<refaddr()|Scalar::Util/"refaddr EXPR">).  Otherwise, returns C<undef>.
+C<refaddr()> (see L<Scalar::Util>).  Otherwise, returns C<undef>.
 
   if (is_shared($var)) {
       print("\$var is shared\n");
@@ -584,7 +584,7 @@ the error "lock can only be used on shared values" to occur when you attempt
 to C<< lock($hashref->{key}) >> or C<< lock($arrayref->[idx]) >> in another
 thread.
 
-Using L<refaddr()|Scalar::Util/"refaddr EXPR">) is unreliable for testing
+Using C<refaddr()> is unreliable for testing
 whether or not two shared references are equivalent (e.g., when testing for
 circular references).  Use L<is_shared()|/"is_shared VARIABLE">, instead:
 
@@ -623,8 +623,8 @@ Either of the following will work instead:
         ...
     }
 
-This module supports dual-valued variables created using L<dualvar() from
-Scalar::Util|Scalar::Util/"dualvar NUM, STRING">).  However, while C<$!> acts
+This module supports dual-valued variables created using C<dualvar()> from
+L<Scalar::Util>.  However, while C<$!> acts
 like a dualvar, it is implemented as a tied SV.  To propagate its value, use
 the follow construct, if needed: