There have been a few times when I have had to eschew the help of the Net:: or Mail:: modules because I was trying to do things that the modules ... ummmm ... were not really designed to do ( no, really, I was forging mail headers in the cause of good - namely, so the whining users couldn't reply to my email ). I likely could have dug deep into the documentation and figured out how to get the module to jump through the hoops I needed, but it was ( in that case alone ) honestly easier for me to write my own little nasty function to do the work.

I have also been on a few projects where the idea was to ship a module such that it could run on any perl. However, we developed the habit ( if they were pure perl modules ) of either including them in the distro or ( horror ) embedding them directly into the file we distributed ( again, please believe me that the original authors were given full credit and no attempt was made to imply I was smart enough to write all the code ).

There are a few excuses for not using CPAN. They are very few though, and CGI.pm is simply not one of them. That has been part of the core since at least 5.003.

mikfire

In reply to Re: Of third party products, code reviews and module installation...(discussion) by mikfire
in thread Of third party products, code reviews and module installation...(discussion) by tinman

Title:
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, details, 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, summary, 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.