Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
So I've spent a lot of time whipping out perl programs that always get the job done, but I'm haunted by the niggling fact that while my code is effecitve, it's anything but sexy, and often wastes resources.

So I'm thinking to myself, how can I begin to improve my base stock of Perlness? and it comes to me that Modules (a black hole in my Perl education) can go a long way to tightening up both the code and the resources used.

So I ask myself, how do I really start to tackle the plethora of modules out there and what they can do? Now the obvious answer is to simply use the ones you need as you need them. But how to go about starting a tight, useful cluster of Modules on which to build a respectable Module know-how for myself?

So I thought I'd get some viewpoints from the Monk community in the way of the Desert Island Disks theme:

You are stranded on some remote island, programming for some very eccentric concern when a strange virus gets into the perl binary and eats away all possiblity for more than 3 modules. (You have to use your imagination a bit.) You can choose any three modules, but they will be the only ones you can ever use again in your perl programming.

Assuming all other dependancies remain intact, what three modules would you choose and why?


In reply to Desert Island Modules by magnus

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 examining the Monastery: (7)
As of 2024-03-29 08:29 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found