Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

comment on

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

I see many questions being asked on this site, many by relative new-comers to the language. Sometimes the questions require involved answers that make use of non-standard modules. This is good - complex problems are being solved by readily available, tested code.

But...

There are many other occasions, today being one, where the answers could take many, many forms, and given that TIMTOWTDI - no, wait - TIMTOWTDI in Perl, but algorithmically we have geometrically more ways. Ahem. Given that there are many, many ways to do it, sometimes we do not favor an answer that may be just as good, but does not require our new-comer to jump right in and start installing modules - a known difficulty for many at first.

I'd like to suggest that we provide answers using standard modules, when those solutions are adequate. New-comers just don't like installing modules to solve something that can be done with the standard distribution itself. Sometimes, the portability or the encoding just doesn't matter to the OP.

Update: Wow. It looks like people read that as "use core modules over CPAN", which I most definitely did not say. I do not advocate using core over CPAN, unless the result is just as good.

Are people really denying the quantity of module-installation issues that are reported here by new-comers?


In reply to Standard Perl Modules ~ Overkill by pbeckingham

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 pondering the Monastery: (4)
As of 2024-04-23 22:47 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found