From adrian.lawrence@computing-services.oxford.ac.uk Sun Oct 31 15:49:07 2004 From: Adrian Lawrence To: occam-com@ukc.ac.uk Cc: Adrian Lawrence Date: Tue, 2 Mar 1999 11:29:34 +0000 (GMT) Subject: Conflicting Priorities in occam Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 MIME-Version: 1.0 X-Mailer: ELM [version 2.4 PL24 PGP2] Message-ID: Here's another fish to throw in with the hares. An interrupt operator is sometimes defined in CSP. So P EEK(i) Q is a process that behaves as P unless the (interrupt) event i happens when process P is completely dumped, and the subsequent behaviour is that of Q. Maybe the occam would look like this? EEK i ? x Q P Never used it myself. Not sure that I want it. Not very happy with throwing P away completely. Just drawing it to your attention in case it is The Answer. I will post 22K of postscript next with the proper CSPP definition in case you would like it 1) typeset; 2) defined. Adrian -- A E Lawrence, MA., DPhil. adrian.lawrence@oucs.ox.ac.uk. MicroProcessor Unit, 13, Banbury Road, Oxford. OX2 6NN. UK. Voice: (+44)-1865-273274, Fax: (+44)-1865-273275