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: 1108a1,7f8fc37d854731d6 X-Google-Attributes: gid1108a1,public X-Google-Thread: 114809,7f8fc37d854731d6 X-Google-Attributes: gid114809,public X-Google-Thread: 109fba,7f8fc37d854731d6 X-Google-Attributes: gid109fba,public X-Google-Thread: 103376,7f8fc37d854731d6 X-Google-Attributes: gid103376,public From: piercarl@sabi.demon.co.uk (Piercarlo Grandi) Subject: Re: Interesting but sensitive topic to discuss (HELP: - OOP and CASE t Date: 1996/11/09 Message-ID: #1/1 X-Deja-AN: 195507481 x-nntp-posting-host: sabi.demon.co.uk x-disclaimer: Contents reflect my personal views only references: <32813322.41C6@kyebek3.kjist.ac.kr> <55pqr5$136a@grimsel.zurich.ibm.com> <328109CD.6685@concentric.net> <6KRKVf9k3RB@herold.franken.de> <55ud3a$n3e$1@goanna.cs.rmit.edu.au> organization: Home's where my rucksack's newsgroups: comp.object,comp.lang.ada,comp.lang.c++,comp.lang.smalltalk Date: 1996-11-09T00:00:00+00:00 List-Id: Alan Lovejoy writes: > OO programs are systems of interacting **objects**, not systems of > interacting **classes**. ok> jhd@herold.franken.de (Joachim Durchholz) writes: jhd> I think this is a bit misleading. OO program texts are definitely jhd> systems of classes (or, rather, textual representations of jhd> classes). >>> "ok" == Richard A O'Keefe writes: ok> This is an overgeneralisaton. Not every OO language is class ok> based. [ ... consider Self etc ... ] Well, but then they something like prototype based, as you observe. The observation above is, as per your remark, strictly speaking not general enough; but then just saying "OO module" instead of "class" would give it generality. For whether class or prototype based, an OO program is a collection of (OO) modules, and values at runtime are either instances of a class or clones of a prototype. OO programs (as opposed to their executions) do occasionally contain some instances or clones, but this does not justify the observation that "OO programs are systems of interacting **objects**". While the analysis and design of an OO program may/should be based on some mental image of how it is going to be executed, both activities are really about deciding into which ``encapsulated'' concepts and modules to decompose the solution to a problem, and not into which ``interacting'' objects (even if in some languages OO modules are objects, and in some others objects to interact).