Well, I find it hard to believe that the five minutes that it would take you to type perl -MCPAN -eshell followed by install HTTP::Request::Common would be longer than you reinventing everything that module calls, including getting it right for the general case. That's why I boggle sometimes at the "no module" crowd.

And even if you don't have good net access, I've seen entire CPAN disks on CD-ROM, so no net connection is required.

You also misinterpret Tom Christiansen. The point of PPT is not to reinvent Unix because he can. The point is to give Unix tools to the unwashed Windows masses, which he considers impoverished. Many of those programs use CPAN modules heavily, so it actually discredits your argument. {grin}

The problem with CGI.pm is not its size: it's that there's so many things to do to handle CGI in general. Every time I've seen something scaled down, it didn't handle something that would eventually have to be handled by adding more code, which already existed in CGI.pm. And CGI.pm is already very agressive at being a "compile as you go" module, minimizing startup cost.

OK, do you have any objections other than those to using CPAN modules? Bring them on. {grin}

-- Randal L. Schwartz, Perl hacker

In reply to RE: On Perl CPAN modules by merlyn
in thread On Perl CPAN modules by strredwolf

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.