From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 109fba,7f8fc37d854731d6
X-Google-Attributes: gid109fba,public
X-Google-Thread: 103376,7f8fc37d854731d6
X-Google-Attributes: gid103376,public
X-Google-Thread: 114809,7f8fc37d854731d6
X-Google-Attributes: gid114809,public
X-Google-Thread: 10461e,7f8fc37d854731d6
X-Google-Attributes: gid10461e,public
X-Google-Thread: 1108a1,7f8fc37d854731d6
X-Google-Attributes: gid1108a1,public
From: nickt@bain.oz.au (Nick Thurn)
Subject: Re: Interesting but sensitive topic to discuss (HELP: - OOP and CASE
 t
Date: 1996/11/11
Message-ID: <56632p$g2e@plath.bain.oz.au>#1/1
X-Deja-AN: 195731658
references: <32813322.41C6@kyebek3.kjist.ac.kr> <55u84o$k0i@plath.bain.oz.au>
 <3283027E.25FA@concentric.net>
followup-to: 
 comp.object,comp.lang.ada,comp.ai,comp.lang.c++,comp.lang.smalltalk
organization: Bain & Company
newsgroups: 
 comp.object,comp.lang.ada,comp.ai,comp.lang.c++,comp.lang.smalltalk
Date: 1996-11-11T00:00:00+00:00
List-Id: <comp.lang.ada>


Alan Lovejoy (alovejoy@concentric.net) wrote:
> Nick Thurn wrote:
> > 
> > alovejoy@concentric.net wrote 06.11.96:
> > >
> > > Class inheritance is an abstraction mechanism for code sharing.
> > > It has
> > > nothing much to do with architecture or design of a program.
> > >
[...]
> > So what pray tell *is* to do with architecture and design?
> 
> Architecture is a question of the division of responsibility among the
> objects and subsystems within a system.  It is about the roles that objects
> play, the relationships among and interactions between objects, and of how 
> objects collaborate to carry out their responsibilities.  Design is the
> process of converting a set of requirements into a specification of the
> types of objects than can exist and how objects of the specified types
> will operate as a system to satisfy the requirements.
> 
I totally agree! 

But objects are described by a text (smalltalk or otherwise) 
as classes that may be related by inheritance, containment or usage. 
Inheritance is not just code organisation (although it does organise code). 

I think there is a chicken and egg problem here. Architecture is expressed
in code and code is organised by architecture. My issue (and where I think
we agree) is that architecture is *more* important than code organisation
because:
	it is more fundamental to correctness of model
	code will be organised anyway by a "good" model
[...]
> 
> You are thinking in terms of some statically-typed
> language that uses classes as type contraints (such as C++).
>
> In a dynamically-typed language such as Smalltalk, it is syntactically legal 
> to send any message to any object.  If the object does not understand the message, 
> an error will be reported at run time.
> 
You are correct, I am thinking in statically typed terms. This does not invalidate
what I said. Sending "any message to any object" still requires the semantics
to be understood. The "typelessness" may be useful or may increase complexity. 
This is a design call and your milage may vary :) 

Nick (my opinions only)

> --
> Alan L. Lovejoy		|==============================================| 
> Smalltalk Consultant	|	Beware of Geeks bearing GIFs!	       |
> alovejoy@concentric.net |==============================================|