I can't think of many situations where multi-threaded perl would be beneficial. I can understand if you were trying to make a Perl/Tk application appear snappier, or have it do graphics (animation) and accept input simultaneously.. but would there be other, more common situations where multi-threaded perl would be considered?<br>
<br><div class="gmail_quote">On Mon, Sep 21, 2009 at 4:43 PM, <span dir="ltr"><<a href="mailto:arocker@vex.net">arocker@vex.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
> If you want high performance, you may find it easier to use<br>
> processes with some form of IPC rather than relying on Perl threads.<br>
<br>
</div>People will keep trying to get the application level to do the OS's jobs.<br>
Unfortunately, threading seems to be a problem even the OS people haven't<br>
solved yet.<br>
<div><div></div><div class="h5"><br>
_______________________________________________<br>
toronto-pm mailing list<br>
<a href="mailto:toronto-pm@pm.org">toronto-pm@pm.org</a><br>
<a href="http://mail.pm.org/mailman/listinfo/toronto-pm" target="_blank">http://mail.pm.org/mailman/listinfo/toronto-pm</a><br>
</div></div></blockquote></div><br>