At 16:52 -0500 12/11/02, Mike Culbertson wrote:
I am attempting to implement Thread::Needs in a threaded app I have written, and I am experiencing the following error, even when I try the sample code provided with the docs:I guess this is a nudge for me to remove Thread::Needs from CPAN. Or at least add doco to it indicating that you shouldn't use this module unless you _really_ know why you want to use it and how it works.
Thread::Needs was an effort by me to be able reduce memory usage for threads. Based on the premise that a load of modules get loaded automagically that you would not need inside a worker thread. However, I think now that it is using the wrong approach. I'm now working at "forks.pm" and "load.pm" to solve these issues in another way.
thread failed to start: Can only call "" in the originating thread at (eval 120) line 7.I would say: dump Thread::Needs from your app unless you are _really_, _really_ running into memory usage problems.
thread failed to start: Can only call "" in the originating thread at (eval 120) line 7.
and so on, one error per worker thread I attempt to start with Thread::Pool. I have found the error message in Pool.pm but I haven't been able to figure out why it is happening. Is anyone familiar with this? Thanks in advance (the code and info follows).
Liz
