the problems have not been totally solved..

That is correct, and I never said that using threads was without problems. But using nodes from 2003 to illustrate the problems with Perl threads today is somewhat like blaming Obama for sending troops to Iraq, or criticising Einstein for the limits of classical mechanics. Things have moved on since then, and any serious discussion would have to take these changes into account.

If you're interested in seriously criticising the usage of threads in Perl programs you should first read up on their current implementation as well as the way threads and processes are handled in multitasking, multi-user operating systems(*). Judging by your posts in this thread (especially your latest reply to BrowserUK) you really have a lot of reading to do, you do not seem to understand how multi-user operating systems work on a fundamental level, and my attempts to explain a few things were obviously fruitless.

(*) I heartily recommend Linux Kernel Development(link is for the upcoming 3rd edition), it goes into a lot of depth but also gives you a clear technical view on how the Linux kernel works and why it works that way.


All dogma is stupid.

In reply to Re^6: Standard way to convert timezone in multithreaded script by tirwhan
in thread Standard way to convert timezone in multithreaded script by whale2

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.