I would love to have an analysis of assumptions made in some code. Because my impression is that the concurrent code is sometimes defined knowing the underlying logic of scheduler and this is not good. As I said to abdel privately in french it would be great to start from my french squeak book (Yes I wrote one long time ago) chapter on concurrent programming and turn it into a pharo chapter. Stef On Tue, Aug 1, 2017 at 1:31 PM, Ben Coman <btc@openinworld.com> wrote:
Not sure I'll have what you're looking for, but to start, do you mean Pharo's green threads or vm native threads? cheers -ben
On Mon, Jul 31, 2017 at 7:38 AM, Alidra Abdelghani via Pharo-users <pharo-users@lists.pharo.org> wrote:
---------- Forwarded message ---------- From: Alidra Abdelghani <alidrandco@yahoo.fr> To: pharo-users@lists.pharo.org Cc: "Stéphane Ducasse" <stephane.ducasse@inria.fr>, farid arfi <arfi_f@hotmail.com> Bcc: Date: Mon, 31 Jul 2017 01:38:58 +0200 Subject: Threads safety in Pharo Hi,
Somebody once evoked the problem of threads safety in Pharo. With a friend of mine who is expert in formal methods and process scheduling, we would like to have a look on it. Does anyone knows a good document describing the problem of Pharo with threads safety or at least any document that we can start with?
Thanks in advance, Abdelghani