Oh dear. I guess my analogy was too big and too abstract. My point was simply that knowledge evolves.

All perl programs are threaded; and starting a second or subsequent thread is trivial. The devil is in the ITC.

Beyond simply listing the already well known mechanisms, there is generically, little more to be said beyond what is already in the documentation.

Picking the right mechanism depends entirely upon the specific of each application. And any single application might conceivably require the use of all ITC mechanisms. Picking the "right" implementation for each piece of communication likewise. It doesn't make sense to use a queue to share the state of a single value. It doesn't make sense to use a shared scalar to share a stream of values.

As for the one stop shop: This is as good a summary of those 3000 posts as I can come up with.

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".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^6: Why it is important to counter FUD. by BrowserUk
in thread Why it is important to counter FUD. by BrowserUk

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.