Thanks. I would like to point out that we have a slightly different take on things, which Perl is making more and more difficult ;-)

On one hand, as you point out, that I completely forgot about, is that modules can load and do nasty things. Ones that do nasty things on require should be taken out behind the barn and shot. On use (aka, import) is another matter. And even then, nasty things such as those Acme modules aren't likely to make it into my corporate build tree :-)

On the other hand, putting CODE refs into @INC is now perfectly plausible - I doubt any solution other than physically loading the module (somehow) will work. Placing your whole VM at risk of infection by whatever is being loaded... having a "use Blather;" line results in Acme::emcA would be problematic in many ways, not the least of which would be manifested at runtime. So, we'll assume, for the minute, that CODE refs in @INC are simply ways to load things in a funny way, and not ways to barrel over the existing code tree.

At the bottom of it all is the fact that I'm not actually using CODE refs in @INC, nor using anything from Acme::*, so I'm going to take a closer look at ExtUtils::MM->version(). I'm not looking for the versions of every single module in the system - just a few. So the idea is to find those modules in @INC and see if ExtUtils::MM can figure out just those specific versions. Thanks!

In reply to Re^2: Checking module (of a level) being installed by Tanktalus
in thread Checking module (of a level) being installed 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.