Lines Matching full:modules

127 perlmodlib - constructing new Perl modules and finding existing ones
131 Many modules are included in the Perl distribution.  These are described
133 files (usually ending in F<.so>) or small pieces of modules to be
139 modules, and the F<.ph> files made by B<h2ph> will probably end up
140 as extension modules made by B<h2xs>.  (Some F<.ph> values may
141 already be available through the POSIX, Errno, or Fcntl modules.)
145 =head2 Pragmatic Modules
179 =head2 Standard Modules
181 Standard, bundled modules are all expected to behave in a well-defined
185 It's possible that not all modules listed below are installed on your
199 To find out I<all> modules installed on your system, including
214 have a B<man> program but it doesn't find your modules, you'll have
219 incomplete) list of the modules that have been further installed on
223 =head2 Extension Modules
225 Extension modules are written in C (or a mix of Perl and C).  They
227 but may also be linked in statically.  Supported extension modules
230 Many popular C extension modules do not come bundled (at least, not
245 Most importantly, CPAN includes around a thousand unbundled modules,
247 modules are:
333 Miscellaneous Modules
339 =head1 Modules: Creation, Use, and Abuse
341 (The following section is borrowed directly from Tim Bunce's modules
367 Do similar modules already exist in some form?
369 If so, please try to reuse the existing modules either in whole or
372 extending or enhancing the functionality of the existing modules.
377 modules, please coordinate with the author of the package.  It
410 Inherit methods from other modules if appropriate.
465 reserves lowercase module names for 'pragma' modules like integer
466 and strict. Other modules normally begin with a capital letter and
520 Having 57 modules all called Sort will not make life easy for anyone
524 If you are developing a suite of related modules/classes it's good
527 Xyz::Model etc. Use the modules in this list as a naming guide.
530 standards for naming modules and the interface to methods in
531 those modules.
533 If developing modules for private internal or project specific use,
541 unique in the first 8 characters. Nested modules make this easier.
543 For additional guidance on the naming of modules, please consult:
646 To be fully compatible with the Exporter and MakeMaker modules you
665    https://www.cpan.org/modules/04pause.html
671 and notify <modules@perl.org>. This will allow anyone to install
675 your modules from your ftp or WWW site into your own directory on
690 =head2 Guidelines for Converting Perl 4 Library Scripts into Modules
779 fragment of code built on top of the reusable modules. In these cases
790 Perl does not enforce private and public parts of its modules as you may