Wonderful, we invent a perfectly good way to group code, make it easy to update, and even work together to fix it and get the word out about bad versions so that everyone shares in the benefits...

Then you come along and ask them to throw that all away over a few paltry microseconds. And chance screwing up the code. And miss out on any redefinition done by other modules through inheritance. And the next time they need to modify the script and just need one more function from CGI they go back to file and try and find it. And they disconnect the functions from the object they work with, potentially breaking all kinds of nice optimizations and friendly features that the full CGI offers. And they wind up pulling over half the module for all the support code anyway and blow off the conditional instantiation so that their code actually winds up bigger in memory.

Here is a hint for the inexperienced monk, your time spent coding is likely to be millions of times more valuable than the time you will save second-guessing and re-inventing the best modules that Perl has to offer. CGI is so good and so valuable to the Perl community that they stuck it in the core so that everyone has it!.

--
$you = new YOU;
honk() if $you->love(perl)

In reply to Re: Re: CGI Benchmarks by extremely
in thread CGI Benchmarks by skeight

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.