[Vm-dev] Where to get Monitor implementation based on primitives?

Eliot Miranda eliot.miranda at gmail.com
Sun Jan 17 17:09:06 UTC 2016

Hi Denis,

> On Jan 17, 2016, at 9:01 AM, Denis Kudriashov <dionisiydk at gmail.com> wrote:
> Hi.
> 2016-01-17 17:47 GMT+01:00 Ben Coman <btc at openinworld.com>:
>> I suspect a problem since it does not check it is the owningProcess
>> before setting owningProcess to nil.  AFAIK, only the owning process
>> should be able to release the mutex.
> Yes. But it is not mutex. It is more abstract thing which allow implement mutex and other concurrency stuff (like ReadWriteLock). That's why I rename CriticalSection to LockOwnership in my proposals. It only contains primitives and no high level methods like #critical:.

Sounds good.  Now would be a good time to submit your preferred versions of the primitives which answer the values that make for more natural variable names.  I'm about to release new VMs, including a 64-bit  Spur JIT.  So I could include the new primitives.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20160117/4e3fb2c3/attachment-0001.htm

More information about the Vm-dev mailing list