> If so, I would think it better to put the onus on the programmer to guard > entry to such critical sections, rather than trying to do it > transparently. Amen. I would have though the 5.005 thread adventure would have driven home that multithreading cannot be made to 'magically' work. The onus (of locking and unlocking) should be on the programmer, not on some mystical hidden logic. (This fata morgana was also discussed on perl 6 lists.) -- $jhi++; # http://www.iki.fi/jhi/ # There is this special biologist word we use for 'stable'. # It is 'dead'. -- Jack Cohen
- our :shared $foo / iThreads Artur Bergman
- our :shared $foo / iThreads Artur Bergman
- Re: our :shared $foo / iThreads David M. Lloyd
- Re: our :shared $foo / iThreads Dan Brian
- Re: our :shared $foo / iThreads Artur Bergman
- Re: our :shared $foo / iThreads Gurusamy Sarathy
- Re: our :shared $foo / iThreads Benjamin Sugars
- Re: our :shared $foo / iThreads Jarkko Hietaniemi
- Re: our :shared $foo / iThreads Gurusamy Sarathy
- Re: our :shared $foo / iThread... Jarkko Hietaniemi
- Re: our :shared $foo / iThreads Gurusamy Sarathy
- Re: our :shared $foo / iThreads Benjamin Sugars
- Re: our :shared $foo / iThread... Gurusamy Sarathy
- Re: our :shared $foo / iTh... Benjamin Sugars
- Re: our :shared $foo / iTh... Gurusamy Sarathy
- Re: our :shared $foo / iTh... Dan Sugalski
- Re: our :shared $foo / iTh... Benjamin Sugars
- Re: our :shared $foo / iTh... Dan Sugalski
