Lines Matching full:modules

8 for writing Perl modules.  It extends the recommendations found in 
13 particularly aimed at authors who wish to publish their modules on CPAN.
21 rather than a tutorial on creating CPAN modules.  It provides a
22 checklist against which modules can be compared to determine whether
104 Stable modules should maintain backwards compatibility
184 Good places to look for pre-existing modules include
194 At the risk of stating the obvious, modules are intended to be modular.
195 A Perl developer should be able to use modules to put together the
202 related modules?
233 Be consistent with existing modules.
251 Authors of similar modules, or modules with similar names, may be a good
316 Large numbers of other programmers will be using your code modules.
412 operator.  While some modules retain uppercase or hyphenated argument
414 modules should use simple lower case keys.  Whatever you choose, be
428 Modules which are "stable" should not break backwards compatibility
445 DBI and other popular modules; if you choose something else, be sure to
456 modules, which reports its errors from the perspective of the caller.  
668 modules, and which modules to rely on.
670 Most importantly, choose modules which are as stable as possible.  In
677 Core Perl modules
681 Stable CPAN modules
685 Unstable CPAN modules
689 Modules not available from CPAN
693 Specify version requirements for other Perl modules in the
702 All modules should be tested before distribution (using "make disttest"),
703 and the tests should also be available to people installing the modules 
712 Useful modules to help you write tests (with minimum impact on your 
719 Modules should be packaged using one of the standard packaging tools.
721 more platform independent Module::Build, allowing modules to be installed in a
744 time modules, and there are many more.  While it is a rite of passage to