As for autoflush -- what is that, and how would I enable it? What does that do, anyway?

When autoflush is on, it forces a flush on the filehandle after every print. It's generally a good idea for autoflush to be on for STDOUT in CGI scripts. The easiest way to do that is to put $| = 1; near the top of your CGI script.

Read perldoc perlvar for more information on the $| special variable. Also, perldoc IO::Handle contains some info on autoflush.

If I were you, I'd turn it on and keep my fingers crossed. Don't be disappointed if it doesn't work though. I'm guessing it won't.

As for muddling through thousands of lines of messy code... well, I'd rather do that than try to guess. :-)

-sauoq
"My two cents aren't worth a dime.";

In reply to Re: Re: Re: Malformed HTML output by sauoq
in thread Malformed HTML output by simX

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.