If you are selective with your quoting you can suggest anything.

The full, relevant quote is:

My immediate expectation is that when you redirect the output it buffers it, allowing thread 1 to complete the entire workload before thread 2 has had a chance to start

Which I'll break down into 3 parts in reverse order:

  1. allowing thread 1 to complete the entire workload before thread 2 has had a chance to start

    No mention that the small size of the sample dataset gives only the appearance of the identified a "problem".

    Nor that if the dataset was large enough to actually warrant using two threads, then there is no problem.

  2. when you redirect the output it buffers it

    The symptoms, wrongly identified as a "problem", have exactly nothing to do with buffering. Turn buffering off and the symptoms do not change at all.

  3. My immediate expectation is

    Giving responses based upon expectations, when it took about 2 minutes to completely disprove the theory, is willfully misleading.

And the "solution" offered to the (non)"problem"; is just completely unnecessary.

So, yes!

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^3: Redirecting output in Windows cmd prevents second thread from doing anything by BrowserUk
in thread Redirecting output in Windows cmd prevents second thread from doing anything by perluser09

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.