Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!tcdcs!csvax1.cs.tcd.ie!swift.cs.tcd.ie!csaran!cjmchale
From: cjmchale@cs.tcd.ie (Ciaran McHale)
Newsgroups: comp.object
Subject: references wanted
Keywords: inheritance, synchronisation
Message-ID: <1990Jan16.122028.16480@cs.tcd.ie>
Date: 16 Jan 90 12:20:28 GMT
Reply-To: cjmchale@cs.tcd.ie (Ciaran McHale)
Organization: DSG, Dept. of Comp.Sc., Trinity College, Dublin, Ireland.
Lines: 27
To:	NEWSMGR@swift.cs.tcd.ie
CC:
Subj:

-------------
Sorry for any duplication of this message. I tried to post it before but
didn't see it at my site so I presume my attempted posting failed.
-------------

Having just started my Masters (adding a synchronisation mechanism to a
parallel OO language) I'm looking for references in the area of
synchronisation mechanisms. In particular, I'd be pleased if anyone could
point me in the right direction for references to the following:

	1. How to overcome the basic conflict between inheritance and
	   synchronisation.
	2. Powerful synchronisation mechanisms. Semaphores and Monitors are
	   a bit low level. I'm looking for something with similar/more
	   expressive power than (Regular, Open, Predicate) Path Expressions.
	3. Efficient implementation of low level synchronisation primitives.

(You may be wondering what this has got to do with OO programming. Point (1)
above is the answer and hence my posting to this group).


Thanks in advance
Ciaran.

P.S. Please email me. I'll summerise if there's much interest.
-------
cjmchale@cs.tcd.ie