From: Denis A Nicole (D.A.Nicole_at_email.domain.hidden)
Date: 1998-05-27 00:13:46
On Tue, 26 May 1998, phw wrote:
>
> Oyvind,
>
> > Does this hold water:
> >
> > Occam's communication language primitives cannot,
> > like monitors, deadlock by erroneous usage. In this
>
> No! Erroneous channel usage certainly causes deadlock. That's the only
> way deadlock occurs in occam systems. Example:
Do you really mean this, Peter? In occam, deadlock=STOP and thus the two
processes
CHAN OF INT a,b: IF
PAR FALSE
SEQ SKIP
a! 1
b! 1
INT x,y:
SEQ
b? x
a? y
are in every respect identical. This actually causes real issues in model
checking---lots of IFs are potential STOPs.
Oyvind: Yes, I'm still working hard on SPOC. Fixing the occam output mode
has generated a flattened version of your application which provokes bugs
in occ2c's normal C mode when generating AST output. I'm getting there.
Denis A Nicole WWW: http://www.hpcc.ecs.soton.ac.uk/~dan
High Performance Computing Centre Email: dan_at_ecs.soton.ac.uk
University of Southampton Phone: +44 1703 592703
UK. Fax: +44 1703 593903
This archive was generated by hypermail 2.1.7 on 2004-10-31 20:03:56 GMT
© Copyright WoTUG
All rights reserved