not sure how responding to a direct question is belabouring the point (granted the response was not so direct, but it was a somewhat-indirect response to a rather-indirect response to my initial comments). nonetheless, i do understand that it is possible to jump to the wrong conclusion when making a quick read (and even re-read) of posted code. and what i'm suggesting is that there are other helpful tools that one should use to verify one's initial diagnosis. and using those tools is especially appropriate when preparing to post a response that says that the OP is doing something wrong.

In reply to Re^6: Perl && threads && queues - how to make all this work together by Anonymous Monk
in thread Perl && threads && queues - how to make all this work together by xaero123

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.