Re^3: require mystery

in reply to Re^2: require mystery
in thread require mystery

No:

require $pathtool;
[download]

is exactly the same as

require "File::Path";
[download]

which fails. Your other attempt,

eval "require $pathtool";
[download]

evaluates the string, which then looks like

require File::Path;
[download]

which succeeds. Consider using the following code if you want a dynamic module loader:

sub require_package {
    for (@_) {
        (my $file = $_) =~ s-::|'-/-g;
        require "$file.pm";
    };
};
[download]

Other alternatives which I recommend against are UNIVERSAL::require and Module::Load because they both hide fatal errors from you, for example compilation errors in the required modules.

Maybe you might want Module::Pluggable for a plugin system.

Comment on Re^3: require mystery Select or Download Code

Replies are listed 'Best First'.
Re^4: require mystery by Pstack (Scribe) on Sep 06, 2007 at 22:27 UTC
Yes, I see, and like your custom function. The code had been working previously with an expression eval before I altered it to the FIRST block eval. Did you notice how I was thrown off by the success nearby of the SECOND block eval which survived all versions: eval {$pathtool->import("mkpath")}; #OK which would not then seem right either if similarly translated as ..(though it may be right?)..: "File::Path"->import("mkpath");#?? Mmm! cheers Pstack	[reply]
Re^5: require mystery by Corion (Patriarch) on Sep 07, 2007 at 06:17 UTC
Perl allows barewords or strings (which are basically the same, except that a bareword comes without quotes, hence, "bare") as invocants: `File::Path->import(...)` [download] is the same as: `"File::Path"->import(...)` [download] and `my $pathtool = "File::Path"; $pathtool->import(...)` [download] and all three translate to: `File::Path::import("File::Path",...);` [download]	[reply] [d/l] [select]

In Section Seekers of Perl Wisdom