[M3devel] Fwd: Fork bug

[Dragiša Durić]

We can implement specific MUTEX subclass with this behavior and use it where its use can be rationalised and where it is needed/correct-thing-to-do.

This way you get specific behavior without (in eyes of most people) breaking up with what has become normal and expected behavior of MUTEXes.

On 08 Jul 2014, at 21:20, Rodney M. Bates <rodney_bates at lcwb.coop> wrote:

> 
> While we are working on MUTEX, I would like to propose making them
> what I believe is meant by a recursive mutex, that is, one thread
> can lock multiple times, the mutex being released only when the number
> of unlocks catches up with the number of locks.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20140709/6b3adbba/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20140709/6b3adbba/attachment-0002.sig>