You are absolutely right, it would! (and I didn't think of it... Just wanted to avoid checking that log file)

I guess this is the reason why this kind of tricks should be use while coding the script, and not in production...

But I wouldn't want to show such intimate stuff as warnings to the people who surf my site...

Update 2: When Apache waits too long for a script and there is still no output, it seems to kill the subprocess... Then we enter the END block, and the warnings are printed (I guess).

Update: If you are really concerned about this, you can always fork a child, and use the pipe to pass it the warnings... The child will store them in an array or a string, and pass them back when your end of the pipe closes... Much heavier, but feasible.

BEGIN {
    pipe(READ, WRITE);
    *STDERR = *WRITE;
    if(!open(DEBUG, "-|") { # child
        close WRITE; my @w = <READ>; print @w; exit }
    
}

END { close WRITE;
      print '<hr><b>Script warnings</b>',
            '<small><pre>', <DEBUG>, '</pre></small>'
}

[download]
(This is untested)

Question: is the END block executed by the child process? If so, where goes the probable warning about the closed DEBUG handle?

In reply to Re: (tye)Re: Get your script warnings on the page it generates by BooK
in thread Get your script warnings on the page it generates by BooK

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.