Article View: comp.sys.transputer
Article #1685Re: Anarchic protocol ANY (occam2)
From: Conor O'Neill
Date: Tue, 21 May 1991 12:55
Date: Tue, 21 May 1991 12:55
13 lines
1157 bytes
1157 bytes
In article <LLW.91May17095750@corwin.eng.yale.edu> llw@ghostwheel.eng.yale.edu (Louis L. Whitcomb) writes: >Note that ihe implementation of channel communication in the newly >released INMOS ANSI C compiler does *not* suffer from this curious >design flaw. I don't know how you got this impression, but the ANSI C compiler (which was released last August!) uses exactly the same method as occam, and so behaves in the same way. --- Conor O'Neill, Software Group, INMOS Ltd., UK. UK: conor@inmos.co.uk US: conor@inmos.com "It's state-of-the-art" "But it doesn't work!" "That is the state-of-the-art".
Technical Details
Message-ID:
<16170@ganymede.inmos.co.uk>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!sdd.hp.com!wuarchive!uunet!mcsun!ukc!inmos!conor@lion.inmos.co.ukReferences:
<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!usc!sdd.hp.com!wuarchive!uunet!mcsun!ukc!inmos!conor@lion.inmos.co.uk From: conor@lion.inmos.co.uk (Conor O'Neill) Newsgroups: comp.sys.transputer Subject: Re: Anarchic protocol ANY (occam2) Message-ID: <16170@ganymede.inmos.co.uk> Date: 21 May 91 12:55:55 GMT References: <9105152020.AA15174@theory.TN.CORNELL.EDU> <LLW.91May17095750@corwin.eng.yale.edu> Sender: news@inmos.co.uk Reply-To: conor@inmos.co.uk (Conor O'Neill) Organization: INMOS Limited, Bristol, UK. Lines: 13