you can/should also check before loading if it is already loaded
You can, but should you? What benefit is gleaned by doing so?
If I simply double up the array of modules the script runs without error or warning and produces the expected results:
#!/usr/bin/env perl
use strict;
use warnings;
use Module::Load;
my @mods = ('JSON', 'CGI::Lite');
for my $mod (@mods, @mods) {
load $mod;
print "$mod version is " . $mod->VERSION . "\n";
}
| [reply]
[d/l] |
You can, but should you? What benefit is gleaned by doing so?
Mostly performance, depending on what you do. For example, my Maplat Webserver stuff loads/configures lots of "web modules" from XML config files on startup. Each "web module" maps to one of a hundred or so perl modules (but many "web modules" use the same perl module, just with different config options on different URIs). It checks if $VERSION is defined, and if not, it loads the perl module, so it doesn't have to load them multiple times. Seems to save a bit of time on startup, which is quite handy while debugging.
My system also notifies me which perl modules are dynamically loaded (instead of already loaded with "use"), which is also quite useful in some circumstances.
"For me, programming in Perl is like my cooking. The result may not always taste nice, but it's quick, painless and it get's food on the table."
| [reply] |
use will never load a module more than once. It has built-in checking for that, and I'd be willing to bet (without any evidence at all) that allowing it to perform the check would likely be faster than doing your own.
Also, not all modules will have version information, particularly those that are in-house.
| [reply]
[d/l] |
The Module::Load caveats section implies it uses require internally, so, in theory, is already checking.
Of course, that doesn't avoid overhead from needlessly running load, so performance-wise, would make sense if Module::Load did it's own check before doing any work.
| [reply]
[d/l]
[select] |
