Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!magnus.acs.ohio-state.edu!csn!ccncsu!purdue!mentor.cc.purdue.edu!noose.ecn.purdue.edu!samsung!uakari.primate.wisc.edu!sdd.hp.com!usc!snorkelwacker.mit.edu!bloom-beacon!eru!kth.se!sunic!mcsun!ukc!mucs!logitek!hrc63!mrcu!paj
From: paj@mrcu (Paul Johnson)
Newsgroups: comp.object
Subject: Re: concurrency control
Message-ID: <894@puck.mrcu>
Date: 10 Apr 91 10:21:27 GMT
References: <1991Apr4.215238.14067@bingvaxu.cc.binghamton.edu> <5558@laas.laas.fr>
Reply-To: paj@uk.co.gec-mrc (Paul Johnson)
Organization: GEC-Marconi Research Centre, Great Baddow, UK
Lines: 28

In article <5558@laas.laas.fr> robert@droopy.laas.fr (Robert Valette) writes:

>Our starting point is HOOD (Hierarchical OOD) and its notion of active objects
>which are provided with OBCSs (OBject Control Structures).

FLAME ON

HOOD (Hierarchical Object-Oriented Design) is not object-oriented.
Its mostly a disguised version of functional decomposition.  The name
is an oxymoron: object-oriented systems are not hierarchical.

Hood does not allow recursive use between modules, so your usage graph
can only be a DAG.  There is no inheritance.  The notation
distinguishes between `objects' and `data', so if you design a
`customer' object you cannot then store that in your linked list
object.  This is all pretty limiting.

You have been HOOD-winked.

FLAME OFF

(Donning asbestos longjohns)

Paul.
-- 
Paul Johnson                               UUCP: <world>!mcvax!ukc!gec-mrc!paj
--------------------------------!-------------------------|-------------------
GEC-Marconi Research is not 	| Telex: 995016 GECRES G  | Tel: +44 245 73331
responsible for my opinions.	| Inet: paj@gec-mrc.co.uk | Fax: +44 245 75244