in reply to Signaling in forked threads
forks is not threading! And despite it's continued billing as a drop in replacement for threads, it behaves and performs completely differently in every way that is critical: signals, memory, IO, scheduling, semaphoring, locking etc. And refering to forking as "threading" just confuses everyone.
If you can't or won't install a thread-capable build of Perl, then you will have to use fork for your multi-processing needs. So save yourself, and those that follow you, a lot of grief, and learn to use fork, or one of the many good wrappers like: Parallel:ForkManager now. Rather than pretending to use threads via forks which gives none of the benefits of the former, and compounds most of the downsides of both.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Signaling in threads
by ajeet@perl (Acolyte) on Apr 07, 2010 at 11:22 UTC | |
by BrowserUk (Patriarch) on Apr 07, 2010 at 11:37 UTC |