diff options
Diffstat (limited to 'pod')
| -rw-r--r-- | pod/perlapi.pod | 10 | ||||
| -rw-r--r-- | pod/perlmodinstall.pod | 5 | ||||
| -rw-r--r-- | pod/perlmodlib.pod | 15 |
3 files changed, 20 insertions, 10 deletions
diff --git a/pod/perlapi.pod b/pod/perlapi.pod index 32e77d6f07..e0ae4cfb58 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<sv.h> -in the C<svtype> enum. Test these flags with the C<SvTYPE> macro. - =item SvTYPE Returns the type of the SV. See C<svtype>. svtype SvTYPE(SV* sv) +=item svtype + +An enum of flags for Perl types. These are found in the file B<sv.h> +in the C<svtype> enum. Test these flags with the C<SvTYPE> macro. + =item SVt_IV Integer type flag for scalars. See C<svtype>. diff --git a/pod/perlmodinstall.pod b/pod/perlmodinstall.pod index 5f1c62e96d..19ffac98c9 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<and> the diff --git a/pod/perlmodlib.pod b/pod/perlmodlib.pod index c1f4aca6be..b42a2d881c 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<all> 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<find> +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<perldoc> program. If you do +not have a B<find> program, you can use the Perl B<find2perl> program instead, which generates Perl code as output you can run through perl. If you have a B<man> program but it doesn't find your modules, you'll have -to fix your manpath. See L<perl> for details. If you have no -system B<man> command, you might try the B<perldoc> program. +to fix your manpath. See L<perl> for details. =head2 Extension Modules |