Though very useful, these provide more objective qualitee/kwalitee information about a release.

The suggested inspector is something about statistics, and th interpretation of statistics is subjective.

e.g. A release might have full documentation that is way better than the docs of any other module on CPAN, but it is delivered in a high standard set of pdf/odt/docx/html/pod/man separate from the .pm file itself icluding a search engine, a graphical fully configurable Wx/Tk GUI just for the docs and ... (ok, I'll stop, just let your fantasy do the job here). As .pod is detected by M::C::A but *not* by the suggested introspection. Next to that, this new analysis just looks at the number of code/comment/blank/doc lines, not at their content, nor at the spelling or the completeness of covering the actual code. It is completely up to the user to weigh the given numbers. You just cannot come to a guide of what is healthy. I therefor think this new suggested module is fun but (for now) lacks real use for indicating quality.

<shameless plug>See also Release::Checklist</shameless plug>


Enjoy, Have FUN! H.Merijn

In reply to Re^7: CPAN modules for inspecting a Perl distribution? by Tux
in thread CPAN modules for inspecting a Perl distribution? by nysus

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.