Those explanations have happened repeatedly in this venue and others. And maybe we shouldn't be so quick to presume that you've seen them, but then again, the damage that your code causes in propogating a bad meme requires swift innoculation, lest someone see your bad code and not notice the correction.

The cargo culting of "read(STDIN, $buf, $ENV{CONTENT_LENGTH})" in all those "teach yourself CGI in 37 microseconds" has not helped. Maybe I'm particularly sensitive about that, since CGI.pm is just too frickin easy to use, and is already installed with all modern Perl distributions.

-- Randal L. Schwartz, Perl hacker

In reply to Re: Re: (tye)Re: Get input data from STDIN *and* query string by merlyn
in thread Get input data from STDIN *and* query string by EvanK

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.