Michael Peters wrote:
Porta wrote:
I saw it, but unless I use the superloader, it still need to define the
names of the modules I want to use.And, regarding the superloader, I'm lazy
enough to want to use all the packages within a given folder, but not just
every possible module in the world...
Still, a good suggestion.
I usually do something similar with some of my mod_perl programs to preload them
into memory but you could probably do something similar. You could use it like:
Heh, I use Module::Pluggable for that in my startup.pl:
use Module::Pluggable require => 1, search_path => [qw(
My
Other::Stuff
)];
__PACKAGE__->plugins;
That would load everything under My::* and Other::Stuff::*.
(Module::Pluggable is in core)
rhesa
##### CGI::Application community mailing list ################
## ##
## To unsubscribe, or change your message delivery options, ##
## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp ##
## ##
## Web archive: http://www.erlbaum.net/pipermail/cgiapp/ ##
## Wiki: http://cgiapp.erlbaum.net/ ##
## ##
################################################################
