Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask

comment on

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

I have to fully agree with princepawn when it comes to reinventing the wheel in your production environment, but I did want to add that I believe that reinventing the wheel isn't all bad. It is best done on your own system where nobody else has to troubleshoot it when you are gone.

Sometimes, reinventing the wheel is the best way to learn about something. You still have the good code from CPAN and from fellow monks, but learning from your own mistakes isn't always a bad thing. You just don't want to go doing them where it matters to more than just you

Ok, that's my 2 pence


Learning Unix sometimes involves Pain, PaIn, PAIN!!

In reply to Re: The worst amputation possible: Perl proper as Open Source software by jlk
in thread The worst amputation possible: Perl proper as Open Source software by princepawn

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.