Article View: comp.sys.transputer
Article #1677Re: Anarchic protocol ANY (occam2)
From: Bryan Carpenter
Date: Mon, 20 May 1991 10:08
Date: Mon, 20 May 1991 10:08
15 lines
1027 bytes
1027 bytes
In <LLW.91May17095750@corwin.eng.yale.edu> llw@ghostwheel.eng.yale.edu (Louis L. Whitcomb) writes: >... >The moral of the story: If you use OCCAM2, use explicit protocols - >even though they are cumbersome and restrictive. It is hard to track >down bugs without them. >Note that ihe implementation of channel communication in the newly >released INMOS ANSI C compiler does *not* suffer from this curious >design flaw. I haven't looked at inmos C very closely. How do they get round the "design flaw" (if that's what it is)? Bryan
Technical Details
Message-ID:
<7730@ecs.soton.ac.uk>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!wuarchive!uunet!mcsun!ukc!icdoc!sot-ecs!dbcReferences:
<9105152020.AA15174@theory.TN.CORNELL.EDU> <LLW.91May17095750@corwin.eng.yale.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!wuarchive!uunet!mcsun!ukc!icdoc!sot-ecs!dbc From: dbc@ecs.soton.ac.uk (Bryan Carpenter) Newsgroups: comp.sys.transputer Subject: Re: Anarchic protocol ANY (occam2) Message-ID: <7730@ecs.soton.ac.uk> Date: 20 May 91 10:08:15 GMT References: <9105152020.AA15174@theory.TN.CORNELL.EDU> <LLW.91May17095750@corwin.eng.yale.edu> Organization: University of Southampton, UK Lines: 15