So, the story so far is that some responders avoid the question of the warning against using threads in
threads. Conversely, an anonymous poster claims the warning can simply be removed. My position is that the correct use of Perl threads and forks is best derived from the pre-existing theory (described surprisingly well on Wikipedia). I have two critics Tye and browserUK who on the one hand make no comment about this warning but are clearly knowledgable about the Perl implementation.
My challenge to anyone who wants to participate in the public interest is to engage with me in a competition to propose alternative and accurate documentation to threads that enables the reader to have a clear understanding of when to use threads versus forks. I don't set a time limit and I am starting my own efforts forthwith. Submissions, when ready should be linked in a reply to this topic.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.