I would welcome any insights... I don't have any tuits to pursue that kind of problem with Thread::Pool.Does the LOAD_NOW variable affect the other Thread::* modules that collaborate with Thread::Pool?
I checked whether this might be related to the on-demand loading of subs of Thread::Pool. Forcing loading of all subroutines at compile time (by specifying the environment variable LOAD_NOW) gives identical results, so I think we can rule out that as a problem.
If they're written by me, there is a good chance. Check the Required Modules section in the pod: if "load" is mentioned, it should work.
Using Event-0.87, Thread::Pool 0.32 and perl 5.8.2/cygwin
Ah... Cygwin... well.. I reproduced the problem on Linux, so that may not have anything to do with it.
Liz
