summaryrefslogtreecommitdiff
path: root/pod/perldsc.pod
diff options
context:
space:
mode:
authorTom Hukins <tom@eborcom.com>2010-03-04 17:38:41 +0000
committerRafael Garcia-Suarez <rgs@consttype.org>2010-03-12 09:48:21 +0100
commitba555bf5eb8f5b1d4d529ec806a7fef2f337c342 (patch)
tree5f8e42eab99b66ce6b8b9ab4ecd6d8db27bdfd97 /pod/perldsc.pod
parent04c2c53e28f4ba728c1eb5803e26f67d44f5672a (diff)
downloadperl-ba555bf5eb8f5b1d4d529ec806a7fef2f337c342.tar.gz
Use POD references to documentation when possible.
Diffstat (limited to 'pod/perldsc.pod')
-rw-r--r--pod/perldsc.pod6
1 files changed, 3 insertions, 3 deletions
diff --git a/pod/perldsc.pod b/pod/perldsc.pod
index db415343c1..b30948c32a 100644
--- a/pod/perldsc.pod
+++ b/pod/perldsc.pod
@@ -85,8 +85,8 @@ distinguishing between arrays and pointers to the same, this can be
confusing. If so, just think of it as the difference between a structure
and a pointer to a structure.
-You can (and should) read more about references in the perlref(1) man
-page. Briefly, references are rather like pointers that know what they
+You can (and should) read more about references in L<perlref>.
+Briefly, references are rather like pointers that know what they
point to. (Objects are also a kind of reference, but we won't be needing
them right away--if ever.) This means that when you have something which
looks to you like an access to a two-or-more-dimensional array and/or hash,
@@ -837,7 +837,7 @@ source code to MLDBM.
=head1 SEE ALSO
-perlref(1), perllol(1), perldata(1), perlobj(1)
+L<perlref>, L<perllol>, L<perldata>, L<perlobj>
=head1 AUTHOR