Re: language syntax for representing concurrency

leew@micrologic.com (Lee Webber)
3 Dec 1996 20:53:46 -0500

          From comp.compilers

Related articles
language syntax for representing concurrency thomasd@cisco.com (Thomas Dejanovic) (1996-12-01)
Re: language syntax for representing concurrency silver@zko.dec.com (Brian Silver) (1996-12-03)
Re: language syntax for representing concurrency bm@cs.columbia.edu (Blair MacIntyre) (1996-12-03)
Re: language syntax for representing concurrency leew@micrologic.com (1996-12-03)
Re: language syntax for representing concurrency gtr@ast.cam.ac.uk (Guy Rixon) (1996-12-07)
Re: language syntax for representing concurrency radenska@cs.uiuc.edu (Boyana Norris) (1996-12-07)
| List of all articles for this month |

From: leew@micrologic.com (Lee Webber)
Newsgroups: comp.compilers,comp.programming.threads
Date: 3 Dec 1996 20:53:46 -0500
Organization: Pioneer Global
References: 96-12-016
Keywords: parallel, design

On 1 Dec 1996 22:55:21 -0500, Thomas Dejanovic <thomasd@cisco.com>
wrote:


>I'm in the process of designing a concurrent OO language. It will
>probably end up being for my amusment only, but I have hopes :-)
>
>Anyway I'm having trouble comming up with a clear readable syntax
>to indicate concurrent processes. I do not want the system to
>start from a single main and spawn all the threads, I want it to
>start up with a number of treads executing concurrently and
>comunicating with each other.


The simplest _syntax_ to describe concurrency I know is the ISE
proposal for concurrent Eiffel: a reference to an object that is to
operate in a separate thread, or the class definition if all objects
of that type are to occupy threads, is tagged with the keyword
'separate'.


That's all there is to it syntactically. The semantics are sort of
tricky, however. See the following URL for the full scheme:


http://www.eiffel.com/doc/manuals/technology/concurrency/CONCURRENCY.html


Note (for c.p.t.) that the scheme is not "Thread"-specific.


--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.