At 01:56 PM 7/29/02 +0200, Arthur Bergman wrote: >>At 10:44 AM 7/29/02 +0100, Tim Bunce wrote: >>>"Thread::Needs" isn't a very descriptive name - it's too general. >>>Something like "Thread::NeedsModules" would be better. >>Hmmm... if that's the only problem you have with it, I'm glad... ;-) >I have been thinking maybe it should be called Thread::Modules; > >use Thread::Modules qw(foo bar baz); #these must be cloned >no Thread::Modules qw(don't need this); #these should not be cloned
Thread::Modules gives me the impression that you're listing modules that should be C<use>d within the thread only. Which is not what it does. And telling a thread which modules to use, is action at a distance. But it could be useful... I guess we need to find a way to emphasize that the module _removes_ modules from the memory of a thread _when_ the thread has started. It doesn't add anything, it merely removes stuff that we don't need after it has been copied. I agree, we need a better way for specifying which modules wind up in which threads, but this is the best thing I've been able to come up with. And it does work right now, with 5.8.0... Liz
