Completely correct! STDOUT is by default buffered. There are a lot of ways that this can "fool you". For example I have one .pl program that runs for many hours, but is not very verbose. $>long_prog.pl >somefile. You watch the size of somefile and it's not getting bigger! But yes, it does get "bigger" it just takes awhile for that to show up in the file size results. It can be that the buffer is like 4KB - Mileage varies. If you have a debug or error statement that prints to STDERR, that can fool you when watching the terminal...the time sequence may be off ...a "normal print" to STDOUT may show up on the screen after a print to STDERR even if the "normal print" happened first. I think we are in agreement here. I don't see any issue.

In reply to Re^5: Break perl foreach loop by Marshall
in thread Break perl foreach loop by pvecchio

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.