Similar to Module::Pluggable but instantiates plugins as soon as they're
found, useful for code generators like Class::DBI::Loader.
This module behaves exactly the same as Module::Pluggable, supporting
all of its options, but also mixes in the call_plugins method to
your class.
Provides a simple but, hopefully, extensible way of having 'plugins'
for your module. Obviously this isn't going to be the be all and
end all of solutions but it works for me.
Essentially all it does is export a method into your namespace that
looks through a search path for .pm files and turn those into class
names.
Optionally it instantiates those classes for you.
Module::Recursive::Require - This class require module recursively.
p5-Module-Refresh
=================
This module is a generalization of the functionality provided by
Apache::StatINC. It's designed to make it easy to do simple
iterative development when working in a persistent environment.
This program automates Perl module releases. It makes the distribution,
tests it, checks that CVS is up to date, tags CVS, uploads it to the
PAUSE anonymous FTP directory and to the incoming directory for
SourceForge.net, claims it on PAUSE for your CPAN account, and releases
it on SourceForge.net.
p5-Module-Reload
================
Similar to Apache::Reload, this module allows a running perl program to reload
all its libraries. Very useful for developing perl servers.
When Perl pulls a file via require, it stores the filename in the global hash
%INC. The next time Perl tries to 'require' the same file, it sees the file in
%INC and does not reload from disk. This module's handler iterates over %INC
and reloads the file if it has changed on disk.
Module::Runtime::Conflicts provides conflicts checking for Module::Runtime,
which had a recent release that broke some versions of Moose. It is called from
Moose::Conflicts and moose-outdated.
This module scans potential modules used by perl programs, using line-by-line
analysis and elaborate heuristics.
Module::Setup is very simply module start kit.
When the module-setup command is executed first, a necessary template
for ~/.module-setup directory is copied.