Re: [Pharo-dev] Semaphore and Mutex changes summary

2016-01-07 14:05 GMT+01:00 Denis Kudriashov <dionisiydk@gmail.com>:

It is also explain why we should deprecate Semaphore>>critical: and use Mutex>>critical: instead. That's second change.

So we want to move 4 Semaphore methods to Mutex:

- critical: mutuallyExcludedBlock

It will relies on new Semaphore method waitIfInterrupted: which block is executed when waiting process terminated at point where lock was not acquired. Slice for this already in inbox.

It was wrong idea. I stop slice for the better solution. I will post about it later