And, in general, has all the downsides of eval STRING: code injection.
...
Avoids eval STRING horrors.

What is it that's so horrific about string eval? At the bottom of any file inclusion there's eval STRING! Perl has taint mode.

Your third example 

(my $filename = $module) =~ s[::][/]g;
$filename .= '.pm';
eval { require $filename };
my $obj = $module->new($options);

[download]

isn't any bit less frightening, since nothing is done to remove '.' from @INC ...

That said, I a) use the first two forms mostly, the third form only if I have to construct non-standard paths; b) I'm feeling happy with that; c) I'd recommend "that what fits best"[tm] and d) uhm, well, there's TIMTOWDTI, laziness, and such... ;-)

In reply to Re: Loading arbitrary modules by shmem
in thread Loading arbitrary modules by Tanktalus

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.