Re: threads question

The simplest solution is to use one or more instances of Thread::Queue to pass the data between your threads.

A super search for "Thread::Queue" will turn up many examples to get you started.

Examine what is said, not who speaks.

"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon

Comment on Re: threads question

Replies are listed 'Best First'.
Re^2: threads question by Forsaken (Friar) on Jul 17, 2004 at 13:26 UTC
Ah, indeed, silly me. Never thought all the Thread::something modules were actually intended to work with the threads module, due to the difference in name. Looks like a whole lotta sexy code just waiting for me to put it to good use. Many thanks indeed.	[reply]
Re^3: threads question by BrowserUk (Patriarch) on Jul 17, 2004 at 16:58 UTC
Yes. The namespaces are confusing. Unfortunately, several of the Thread::* modules intended for use with 5005threads are non-useful with ithreads, but will likely never be removed or upgraded. The good news is that liz generated several new modules that are. Thread::Use is small and rather uninspiringly named, but extremely Use-ful. Examine what is said, not who speaks. "Efficiency is intelligent laziness." -David Dunham "Think for yourself!" - Abigail "Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon	[reply]
Re^4: threads question by Forsaken (Friar) on Jul 17, 2004 at 20:21 UTC
it is indeed :-) saves me a good chunk of memory even with just 5 threads running. Tx for the tip.	[reply]
Re^5: threads question by Anonymous Monk on Jul 18, 2004 at 08:15 UTC
Re^6: threads question by BrowserUk (Patriarch) on Jul 18, 2004 at 10:57 UTC