> lo...@cs.utexas.edu (Logan Shaw) wrote in message <news:firstname.lastname@example.org>... > > ... > > There's also the fact that some problems are expressed more easily > > in terms of threads. If you have are handling several interactive > > sessions or several concurrent web requests, it makes things easier > > if you have a thread associated with each session or request.
> Wow, that was a very clear explanation, and the reasoning makes > perfect sense. Thanks. :)
> Now my (more Perl-related) question becomes: are threads still > unreliable as of 5.6.1? (Specifically ActiveState for Win, if that > makes a difference.) Or is the word still, "Wait for ithreads in 6"?
You can fork() reliably in 5.6.1, and *should* be able to use threads reliably in 5.8 (coming in May! I think it's May, anyway...). If you're wondering how stable the threads for 5.8 will be, you can download 5.7.2, and try using them: what you see is pretty close to what you will get.