Now you may wonder why Perl ithreads didn't use fork()? Wouldn't that have made a lot more sense? Well, I wasn't involved in the thread design process at the time, so I have no idea what the exact reasons were.
Hysterical raisins--surprisingly good ones, but still
hysterical raisins. ithreads were originally developed
to emulate fork(1) on Windows, which doesn't have
such a call; thus, they couldn't be built on
Besides, as your forks module demonstrates,
most of the speed wins of using fork(1) on
systems that have it would be lost in the interthread
communications. The general consensus seems to be that
you should use ithreads in code with a lot of
interthread communications, a magic open (or
such) in code with a little communication, and a raw
fork in code with very little communcation.
There is no sig.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.