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) |
From: | Brian Silver <silver@zko.dec.com> |
Newsgroups: | comp.compilers,comp.programming.threads |
Date: | 3 Dec 1996 20:47:20 -0500 |
Organization: | DECthreads |
References: | 96-12-016 |
Keywords: | parallel, design |
Thomas Dejanovic wrote:
> So does anyone have some neat ideas for representing such a
> concept _clearly_ in an OO way in a language ?
How about:
process = {thread1, thread2, thread3, ..., threadn};
or
subsystem1 = {thread1,...,threadn};
process = {subsystem1, thread1,..., threadn, subsystemn};
Where "threadn" represents threadn's start routine.
Or, something like
define thread1 is_a_member_of process1;
or
define thread1 is_a_member_of subsystem1;
Brian "Ye' Ol' Set Membership"
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.