Add documentation on the advantages of perldoc for man users to perl.pod

Thanks.

Signed-off-by: H.Merijn Brand <h.m.brand@xs4all.nl>

diff --git a/AUTHORS b/AUTHORS
index b6d7f6e..0ae9f80 100644 (file)
--- a/AUTHORS
+++ b/AUTHORS
@@ -929,6 +929,7 @@ Raymund Will                        <ray@caldera.de>
 Redvers Davies                 <red@criticalintegration.com>
 Reini Urban                    <rurban@x-ray.at>
 Renee Baecker                  <module@renee-baecker.de>
+Reuben Thomas                  <rrt@sc3d.org>
 Rex Dieter                     <rdieter@math.unl.edu>
 Rhesa Rozendaal                        <perl@rhesa.com>
 Ricardo Signes                 <rjbs@cpan.org>

diff --git a/pod/perl.pod b/pod/perl.pod
index d3f9c05..d218491 100644 (file)
--- a/pod/perl.pod
+++ b/pod/perl.pod
@@ -280,6 +280,12 @@ aux a2p c2ph h2ph h2xs perlbug pl2pm pod2html pod2man s2p splain xsubpp
 On a Unix-like system, these documentation files will usually also be
 available as manpages for use with the F<man> program.
 
+Some documentation is not available as man pages, so if a
+cross-reference is not found by man, try it with L<perldoc>.  Perldoc can
+also take you directly to documentation for functions (with the B<-f>
+switch). See C<perldoc --help> (or C<perldoc perldoc> or C<man perldoc>)
+for other helpful options L<perldoc> has to offer.
+
 In general, if something strange has gone wrong with your program and you're
 not sure where you should look for help, try making your code comply with
 B<use strict> and B<use warnings>.  These will often point out exactly