Re^6: Win32 and threads;

However, if you can show me a useful application of using more than half a dozen or so simultaneous threads, I'll show you a better way :)

I don't mean to disagree with this - in fact I think you're right, but I would be very interested to read an elaboration on this claim from you. Would you?

Comment on Re^6: Win32 and threads;

Replies are listed 'Best First'.
Re^7: Win32 and threads; by BrowserUk (Patriarch) on Jul 11, 2004 at 23:19 UTC
The smiley was intended to defuse the statement from being taken as definitive, but in general, I'll stand by it (in the context of Perl programs using ithreads on Win32). But, it's difficult to elaborate upon for the general case. I've yet to see a good use of large numbers of iThreads. And I've yet to find the right way to write the type of application that might make use of large numbers of threads using perl. 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]

Replies are listed 'Best First'.

Re^7: Win32 and threads;
by BrowserUk (Patriarch) on Jul 11, 2004 at 23:19 UTC

The smiley was intended to defuse the statement from being taken as definitive, but in general, I'll stand by it (in the context of Perl programs using ithreads on Win32).

But, it's difficult to elaborate upon for the general case. I've yet to see a good use of large numbers of iThreads. And I've yet to find the right way to write the type of application that might make use of large numbers of threads using perl.

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]