Re: our :shared $foo / iThreads

[Gurusamy Sarathy]

On Thu, 03 May 2001 12:37:52 CDT, Jarkko Hietaniemi wrote:
>> 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.

Sorry, I'm not convinced that all the locking should be at the control
of the programmer.

Locking needed to avoid deadlocks should be at the control of the
programmer.  Any and all locking needed to avoid coredumps and memory
corruption should be the sole province of the perl guts.  :-)


Sarathy
[EMAIL PROTECTED]