Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!sdd.hp.com!elroy.jpl.nasa.gov!lll-winken!aunro!alberta!naren From: naren@cs.UAlberta.CA (Narendra Ravi) Newsgroups: comp.object Subject: Re: Concurrency vs Inheritence Message-ID: Date: 3 Apr 91 23:52:04 GMT References: <908@antares.Concordia.CA> <2488@calmasd.Prime.COM> Sender: news@cs.UAlberta.CA (News Administrator) Organization: University of Alberta, Edmonton, Canada Lines: 28 wlp@calmasd.Prime.COM (Walter Peterson) writes: >In article <908@antares.Concordia.CA> bcheung@omicron.cs.concordia.ca (CHEUNG yik-chi) writes: >>Hi, >> >>I just begin working on concurrency vs inheritence. > ^^ >Concurrency VERSUS inheritance ??? >I really do not see that there is any conflict here. Perhaps the >original poster or others with the same view could expand upon >what this conflict might be. The two concepts are related. Given an inheritance hierarchy, it is difficult to distribute it across machines without replicating information. -- -- Naren Narendra Ravi Email : naren@cs.ualberta.ca -- -- Naren Narendra Ravi Email : naren@cs.ualberta.ca