[squeak-dev] Future examples (Re: Inbox: #future keyword for
asynchronous message invocation)
stephen at pairhome.net
Thu Dec 17 22:11:53 UTC 2009
On Thu, Dec 17, 2009 at 4:28 PM, Andreas Raab <andreas.raab at gmx.de> wrote:
> Future messages allow you to use concurrency in cases where it would be
> very hard to synchronize with locks - in the above I would have to guard all
> the modifications of the scrollbar's value by some lock but using the future
> message allows us to introduce a level of concurrency that would be
> difficult to achieve otherwise.
What is the scope of this safety with respect to shared state and mutation?
Are you essentially treating the entire image as a vat (in the E sense)?
Is it per morphic project? Or something else?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev