Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Great feedback on this poll!

A couple I haven't seen mentioned:

  • Track record of backwards compatibility: Does the author have a history of keeping existing things stable from release to release, or are previous pieces of functionality continuously changed for no seemingly apparent reason (and without a reasonable amount of time with notices of deprecation or mods that will definitely break stuff)? (ie. will I have to frequently update my distributions due to frequent changes to the dependency)
  • A good Changes file. Clear, concise (point-form, not overly verbose) information from version to version, possibly including references to tickets etc
  • A *quality* test suite. I can write a 50,000 test test-suite, but how many of those tests are of decent quality? Can I read through tests for example code snips if necessary? Is the suite well laid out with informative file names?
  • Test history... does the distribution have a poor failure rate across several releases?
  • Does the code unnecessarily piss all over my namespace(s)?
  • Does the code blatantly do ridiculous magic for no apparent reason that could cause me hard-to-identify bugs later on down the road?

There are several more that I can't think of right now. Note that some of the above I'm going a bit overboard on... I don't read through every line of code before deciding to use a module. I do however have a reasonable glance to check for consistency, blatantly obvious weirdness, naming of various items (ie. names like sub_a(), sub_b(), my $var1, $var2 etc are red flags) etc

In reply to Re: I am most likely to install a new module from CPAN if: by stevieb
in thread I am most likely to install a new module from CPAN if: by hippo

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others about the Monastery: (7)
    As of 2020-10-25 22:44 GMT
    Find Nodes?
      Voting Booth?
      My favourite web site is:

      Results (249 votes). Check out past polls.