Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

A community collection like CPAN is definitely a “mixed bag,” and no doubt a fair number of the vegetables in that bag are rotten, but most of them are quite good. There are a handful of routines that have been around a long time, have strong outside web-sites demonstrating active support, have a large number of request tickets posted against them but none of them are still “open,” and so on. The hallmarks of kwalitee are there to be found.

Before starting on a project, I always find it useful to spend some “kwalitee tyme” looking carefully through CPAN to see what is out there. In particular, I want to see the approach that various authors have used, knowing that they felt that the work was useful enough that they wanted to make it public. Sometimes that code is a real eye-opener.

What I don't try to do is to use the CPAN code as a “hope-it-works black-box.” I'm happy to use it as a short-cut to what I am doing, and even as a strong influencer of my design ideas, but not as a replacement for my own thinking. (I think you understand what I am trying to say here. I am on cup-of-coffee number-one.)


In reply to Re: Choosing modules - community matters or just technical merits? by sundialsvc4
in thread Choosing modules - community matters or just technical merits? by zby

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others imbibing at the Monastery: (6)
As of 2024-04-19 11:00 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found