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: 1108a1,7f8fc37d854731d6 X-Google-Attributes: gid1108a1,public X-Google-Thread: 114809,7f8fc37d854731d6 X-Google-Attributes: gid114809,public X-Google-Thread: 10461e,7f8fc37d854731d6 X-Google-Attributes: gid10461e,public From: vlad@world2u.com (vlad) Subject: Re: Interesting but sensitive topic to discuss (HELP: - OOP and CASE tools) Date: 1996/11/10 Message-ID: #1/1 X-Deja-AN: 195609099 x-nntp-posting-host: i123.254.world2u.com references: <32813322.41C6@kyebek3.kjist.ac.kr> <55pqr5$136a@grimsel.zurich.ibm.com> <328109CD.6685@concentric.net> <55v177$ufo@grimsel.zurich.ibm.com> x-nntp-posting-user: (Unauthenticated) x-trace: 847598664/24446 newsgroups: comp.object,comp.lang.c++,comp.lang.ada,comp.lang.smalltalk,comp.ai Date: 1996-11-10T00:00:00+00:00 List-Id: Paul_Gover@uk.ibm.com wrote: >However, I disagree when it comes to design; this might be a >difference in our view of where to separate design from coding. My view is that design >includes implementation detail such as inheritance. I most certainly consider that >"OO development methods" should address it. Design of what? Design of a class or design of a system. In the design of a system you don't need to bother with inheritance. What about objects, that are not defined by classes or what about objects, which can change it's class at run-time. In the design of a system the most important thing is a object interface and how it coopeates with other objects. If you design a class, then you will find inheritance usefull. Of course the "inheritance" can be replace by delegating and then we even don't need classes. So inheritance is a implementation detail, that is not important in design of your application. It is my view and I may be wrong. >I think from your statement about converting to equivalent programs indicates you >consider implementation to be outside the scope of the design (since you describe two >different implementations for the same design); in that case, do you think that >questions of inheritance and so forth are not part of the development method? >I think this is dangerous; in your example, the coverted program has large amounts of >duplicated code, so making changes is harder because the programmer has to find all >occurrences of the duplicated code, and we have lost one of the benefits of OO. >Paul Gover >IBM Warwick Development Group >Mumbling for myself, not IBM Vlastimil Adamovsky ** C++ and Smalltalk consultant ** * http://www.stepweb.com *