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: 1108a1,7f8fc37d854731d6 X-Google-Attributes: gid1108a1,public X-Google-Thread: 10461e,7f8fc37d854731d6 X-Google-Attributes: gid10461e,public X-Google-Thread: 114809,7f8fc37d854731d6 X-Google-Attributes: gid114809,public X-Google-Thread: 103376,7f8fc37d854731d6 X-Google-Attributes: gid103376,public From: Anthony Menio Subject: Re: Interesting but sensitive topic to discuss (HELP: - OOP and CASE tools) Date: 1996/11/12 Message-ID: #1/1 X-Deja-AN: 197111134 references: <32813322.41C6@kyebek3.kjist.ac.kr> <55pqr5$136a@grimsel.zurich.ibm.com> <328109CD.6685@concentric.net> <32873B68.167EB0E7@arscorp.com> content-type: TEXT/PLAIN; charset=US-ASCII organization: Montclair State University mime-version: 1.0 newsgroups: comp.object,comp.lang.c++,comp.lang.ada,comp.lang.smalltalk,comp.ai Date: 1996-11-12T00:00:00+00:00 List-Id: On Mon, 11 Nov 1996, Daniel Drasin wrote > You are both right (and wrong). The question is, what is the point of > the distinction. P.G. Just 'cause you can't "see" the objects doesn't > mean that they're not there. E.g. A psychiatry textbook will describe > behavior of "humans," "men," and "women." These are types but clearly > in actual application, these "laws of psychiatry" apply to the actual > individual people involved. > > Smalltalk, C++, and java use what's called "class-based programming" > which > means that the behavior of individual objects is described by its > type or class. Therefor classes will be manipulated in order to affect > the behavior of objects. Which leads back to by origional question: > What is the point of the distinction? What is the point of saying > that an OO program is the interaction of objects (and not classes)? > If the point is to direct the student to understand the runtime behavior > that needs to be focused on, then objects are what the program consists > of (ognoring the reflective meta abilities...). However, if the aim > is to understand what must be created at compile time in order to > create a program, then "classes" are the elements are the program. > > Dan The classes are simply blue prints of the the objects which can be created, and thus describe the attributes and behavior of objects. The runtime system consists of objects and these are what must be specified and the interactions between them at implementation time. Your source code consists of instances of these classes and the messages you designate to have happen and the states and messages these result in across the system. The messages you designate might simply create the system (constructors) and determine interobject relations and than wait for user messages.The system you build is thus described by the objects created and the methods you specify to be called and the states these create and manipulate a runtime. Classes are simply blueprints and thus describe the domain of states and possible behaviors an instance can assume. A software system consists of assumed behavoirs and determined behavoirs in response to runtime user messages and thus of objects. In terms of source code your system is really object creations and method invocations that occur at runtime implied by code like the following: Application my_App(); myapp.setDbase("Oracle"); FileSever netsever10(CURRENT_IP); requestObject *action= application.idle(); if (interupt) { netserver.request(requestObject); myapp.continue(requestObject); } further more even this is simply a blue print for the system as a whole the true system only exists at runtime however even its implementation description refers to definite articals to be created ie objects. I think this distinction maybe subtle but is important. Anthony Menio I.S. Student menio@pegasus.montclair.edu Your power is your ideas, your ideas are products of perception, your perception is the product of your architecture, architecture is everything - me