Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!eru!luth!sunic!mcsun!hp4nl!media01!pkr
From: pkr@media01.UUCP (Peter Kriens)
Newsgroups: comp.object
Subject: Re: The essence of objects...
Keywords: oops objects co2 objective c
Message-ID: <1288@media01.UUCP>
Date: 13 Jul 90 08:43:33 GMT
References: <1280@media01.UUCP> <1964@runxtsa.runx.oz.au>
Organization: Mediasystemen, Netherlands
Lines: 24

>In article <1280@media01.UUCP> pkr@media01.UUCP (Peter Kriens) writes:
>>The essence of objects...
>>
>>	The essence of oops is to specify 
>>	a functionality only once.

Tim Menzies answers
> yes, yes, yes. oop is a way of normalising procedural knowledge. database
> designers realised that we had to normalise data decades ago. now, we
> normalise code as well.

This answer seems to imply that we now normalize code. I think we should
normalize our code, one way or the other. But it seems that the
database designers have some formal logic, and at least some understanding
of what it means to normalize data. I wouldn't know where to start
to normalize code.

Is there anyone who does? Are there formal techniques like normalizing
which can be adapted to software design?

I would love to hear about those.

Peter Kriens
Mediasystemen