From: Gurusamy Sarathy Date: Sun, 19 Mar 2000 09:20:22 +0000 (+0000) Subject: mention how to look up perllocal.pod (from Michael G Schwern) X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=6175e92675be1342fe51e34be66eb32d50cd8c0b;p=p5sagit%2Fp5-mst-13.2.git mention how to look up perllocal.pod (from Michael G Schwern) p4raw-id: //depot/perl@5827 --- diff --git a/pod/perlapi.pod b/pod/perlapi.pod index 32e77d6..e0ae4cf 100644 --- a/pod/perlapi.pod +++ b/pod/perlapi.pod @@ -1597,17 +1597,17 @@ false, defined or undefined. Does not handle 'get' magic. bool SvTRUE(SV* sv) -=item svtype - -An enum of flags for Perl types. These are found in the file B -in the C enum. Test these flags with the C macro. - =item SvTYPE Returns the type of the SV. See C. svtype SvTYPE(SV* sv) +=item svtype + +An enum of flags for Perl types. These are found in the file B +in the C enum. Test these flags with the C macro. + =item SVt_IV Integer type flag for scalars. See C. diff --git a/pod/perlmodinstall.pod b/pod/perlmodinstall.pod index 5f1c62e..19ffac9 100644 --- a/pod/perlmodinstall.pod +++ b/pod/perlmodinstall.pod @@ -91,6 +91,11 @@ While still in that directory, type: Make sure you have appropriate permissions to install the module in your Perl 5 library directory. Often, you'll need to be root. +Perl maintains a record of all module installations. To look at +this list, simply type: + + perldoc perllocal + That's all you need to do on Unix systems with dynamic linking. Most Unix systems have dynamic linking--if yours doesn't, or if for another reason you have a statically-linked perl, I the diff --git a/pod/perlmodlib.pod b/pod/perlmodlib.pod index c1f4aca..b42a2d8 100644 --- a/pod/perlmodlib.pod +++ b/pod/perlmodlib.pod @@ -802,17 +802,22 @@ By-name interface to Perl's built-in getpw*() functions To find out I modules installed on your system, including those without documentation or outside the standard release, -jus tdo this: +just do this: % find `perl -e 'print "@INC"'` -name '*.pm' -print -They should all have their own documentation installed and accessible -via your system man(1) command. If you do not have a B +To get a log of all module distributions which have been installed +since perl was installed, just do: + + % perldoc perllocal + +Modules should all have their own documentation installed and accessible +via your system man(1) command, or via the C program. If you do +not have a B program, you can use the Perl B program instead, which generates Perl code as output you can run through perl. If you have a B program but it doesn't find your modules, you'll have -to fix your manpath. See L for details. If you have no -system B command, you might try the B program. +to fix your manpath. See L for details. =head2 Extension Modules