I suspect that had you done the rewrite using
CGI you
would have been done sooner than you were staying with
the broken hand-rolled approach.
And you wouldn't have taken up anyone else's time.
That is why people chant CGI. It is the good
kind of lazy. Takes less work and you come up with
answers that you know you can trust.
The only case where I wouldn't recommend it that I know
of is doing .csv downloads to IE 4.x (may be some OS or
subversion issue as well there). Why? Because if the
browser thinks it is a CGI script, it breaks horribly
in loading Excel. (In fact it takes the path, that
includes the directory "Temporary Internet Files", splits
on the space, and feeds that as 3 files to Excel, none of
which are there.)
In that case I would cheat and store the argument list in
$ENV{PATH_INFO}.
Other than that bug I have not ever heard of any good
reason to not do things right with CGI...
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.