diff options
| author | Jarkko Hietaniemi <jhi@iki.fi> | 2000-12-18 02:49:27 +0000 |
|---|---|---|
| committer | Jarkko Hietaniemi <jhi@iki.fi> | 2000-12-18 02:49:27 +0000 |
| commit | 165c02774acf38ce5b4b57db8b54b3d75ff3d9d8 (patch) | |
| tree | 15c8769b10e80df987c2bad7b00e43d4f28a09bd /pod/perlmodlib.pod | |
| parent | ec68f363483885ed31575a17dede3de9e3bc91da (diff) | |
| download | perl-165c02774acf38ce5b4b57db8b54b3d75ff3d9d8.tar.gz | |
Regen pods.
p4raw-id: //depot/perl@8172
Diffstat (limited to 'pod/perlmodlib.pod')
| -rw-r--r-- | pod/perlmodlib.pod | 26 |
1 files changed, 20 insertions, 6 deletions
diff --git a/pod/perlmodlib.pod b/pod/perlmodlib.pod index c5afea214e..1810e0003a 100644 --- a/pod/perlmodlib.pod +++ b/pod/perlmodlib.pod @@ -114,6 +114,10 @@ Restrict unsafe operations when compiling Package for overloading perl operations +=item perlio + +Configure C level IO + =item re Alter regular expression behaviour @@ -288,10 +292,6 @@ Wrapper around CPAN.pm without using any XS module Warn of errors (from perspective of caller) -=item Carp::Heavy - -Carp guts - =item Class::Struct Declare struct-like datatypes as Perl classes @@ -444,6 +444,10 @@ Create or remove directory trees Portably perform operations on file names +=item File::Spec::Epoc + +Methods for Epoc file specs + =item File::Spec::Functions Portably perform operations on file names @@ -484,6 +488,10 @@ Keep more files open than the system permits Supply object methods for filehandles +=item Filter::Simple + +Simplified source filtering + =item FindBin Locate directory of original perl script @@ -791,7 +799,7 @@ Most importantly, CPAN includes around a thousand unbundled modules, some of which require a C compiler to build. Major categories of modules are: -=over 4 +=over =item * Language Extensions and Documentation Tools @@ -861,7 +869,7 @@ Miscellaneous Modules Registered CPAN sites as of this writing include the following. You should try to choose one close to you: -=over 4 +=over =item Africa @@ -1217,6 +1225,12 @@ If adding a new module to a set, follow the original author's standards for naming modules and the interface to methods in those modules. +If developing modules for private internal or project specific use, +that will never be released to the public, then you should ensure +that their names will not clash with any future public module. You +can do this either by using the reserved Local::* category or by +using a category name that includes an underscore like Foo_Corp::*. + To be portable each component of a module name should be limited to 11 characters. If it might be used on MS-DOS then try to ensure each is unique in the first 8 characters. Nested modules make this easier. |