RSS | Module Info | Add a review of Thread-Pool
Thread-Pool
(0.33)
This module is indeed convenient, but in my opinion there are some serious problems with it.
First, if a thread dies, the error gets lost. I would expect that if one of my jobs dies, that I can get the value of $@ and act on it. There is a workaround: I can wrap all my jobs in some error handler of their own. But that defeats the elegance of code using this module, and still any errors in the error handler get lost.
Second, this module is using 'use load' which causes Log::Log4perl to malfunction. That is certainly one evil heisenbug. It was only because I found a Czech comment in this source file [1] that it didn't take me days of debugging.
[1]: w2c.martin.majlis.cz/w2c/doc-gen/craw...
R. Lamers - 2012-08-15T04:26:26 (permalink)
1 out of 1 found this review helpful.
Was this review helpful to you?
Yes
No
Thread-Pool
(0.32)
This module is awesome. Although I plan to get into the mechanics of Perl threads in the future, this module allowed me to know virtually nothing and utilize threads for something I needed to get done now.
Mark Murray - 2009-02-02T10:49:57 (permalink)
2 out of 2 found this review helpful.
Was this review helpful to you?
Yes
No
Thread-Pool
(0.32)
I am extraordinarily pleased with this module. I was able to convert my hacked-together, first attempt at interpreter threading to a professional, resource-optimized self-limiting pool in a matter of minutes. Full points.
coral - 2004-06-06T22:13:28 (permalink)
1 out of 1 found this review helpful.
Was this review helpful to you?
Yes
No
