I always use strict, -w and fatalsToBrowser when developing,
but today this caused me a huge headache in
a simple script (with no syntax errors) that merely reads a
file, formats the contents, and displays the html.
fine from the command line (with a few uninitialized value
warnings) and could save the output with
perl foo.pl > foo.html
but it would just whirl and give no output via CGI. I found that
the code looks and behaves perfectly via CGI unless
-w and fatalsToBrowser are enabled! Shut
either one off (leaving the other on) and it works fine.
I found a certain loop in the program that seems to cause
this by throwing pairs of =cut around, but the loop seems
mundane and similar to the others.
Is this odd interplay between -w and fatalsToBrowser documented?
Update: I said i'd node the entire script to craft
in a day or two but am finding it difficult to abstract a
simplified example. So i'll just suggest that if your
error-free cgi script mysteriously hangs, turning off
either -w or fatalsToBrowser may help.
dws - Try this for a good html :
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.