I can definitely second all the points. If you want to verify your design
formally, Vereofy (http://www.vereofy.de) is another model checker that
focuses on communication and coordination.
Best, Steffen
Am .10.2019, 08:49 Uhr, schrieb Richard O'Keefe :
(1) Be very clear in your design about
(1) Be very clear in your design about which objects are shared and
which are not.
(2) Immutable objects can be shared safely. Mutable ones are much
much harder to work with.
(3) Lazy initialisation does not work well in concurrent programming,
*except* when you are
constructing an immutable
sometime.
> >
> > Vince
> >
> >
> > From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of
> > Christopher Fuhrman
> > Sent: Tuesday, 15 October 2019 11:39 AM
> > To: Any question about pharo is welcome
> > Subject: Re: [Pharo-use
; Vince
>
>
> From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org
> <mailto:pharo-users-boun...@lists.pharo.org>] On Behalf Of Christopher Fuhrman
> Sent: Tuesday, 15 October 2019 11:39 AM
> To: Any question about pharo is welcome <mailto:pharo-users@lists.p
From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of
Christopher Fuhrman
Sent: Tuesday, 15 October 2019 11:39 AM
To: Any question about pharo is welcome
Subject: Re: [Pharo-users] Concurrency Best Practices + Tests
EXTERNAL: Do not click links or open attachments if you do
Noury - I happened to notice in a recent article about the Rust scheduler (it
caught my eye) it had a section on concurrent testing and a tool they write
called Loom to test all possible permutations and catch errors.
This might be an avenue of investigation for your work ?
An idea any way.
htt
On Wed, 4 Sep 2019 at 21:32, Noury Bouraqadi wrote:
> Hi everyone,
>
> Can I get your input on the following questions :
>
> - What are your best practices and recommendations for developing and
> testing concurrent software?
>
I haven't any formalized advice, but just a scattering of thoughts:
Hi everyone,
Can I get your input on the following questions :
- What are your best practices and recommendations for developing and testing
concurrent software?
- How to discover need for synchronization/critical sections/ when doing TDD?
- How to write code to avoid dead-locks?
Noury
