My thoughts center on a related, if less anti-C, concern. I don't mind that modules require external dependencies, even complex ones. But I completely agree that it would be nice if there was a consistent way to flag them as such.

I am currently working on a perl upgrade project in our environment and part of this upgrade is tracking all the modules we have. The CPAN module does a great job with this with its 'autobundle' and 'check for new versions' features. But what it can't do (that I know of) is track the same info for these external dependencies.

So I'll either have to manually go through and catalog this info, or brute force install each new module and let it bark when the dependencies aren't up to snuff.

If this info was somehow easily available in a standard way from distributions, you could potentially run searches in CPAN, down the dependency tree, to see exactly what would be required.

Another issue is where this external code has to go for various distributions. Some external dependencies need to be installed outside the module install, and it can be difficult to track the locations of these external components.

In reply to Re: Disputation of g0n on the power and efficacy of XS by cbrandtbuffalo
in thread Disputation of g0n on the power and efficacy of XS by g0n

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.