> 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

Reply via email to