Re: >>> Chris Rehm <Mr.AS400@xxxxxxx> 02/20/98 08:37am >>>

** Reply to note from Scott Cornell <CORNELLS@mercyhealth.com> Fri, 20 Feb 1998 
12:34:03 -0500


> I don't do OO coding to any great extent, so this is probably the blind 
>leading the blind.  But, I think the 
> analogy only covers the information hiding advantage of OO, which well 
>structured procedural code has 
> anyway (sorta the point someone made earlier in the thread, eh?)  How about 
>this similar analogy:

No, the analogy covers it all. 

After all, when you define your "Cup of Tea" object, it will inherit the
methods of all the senior classes. So, when you write the "Give tea" method
for the cup, it will invoke senior methods upon needed conditions (ie., if
the cup has tea in it, there is no need to look for a super method, if not
it must go to teapot, if teapot has hot water, there is one method, if not,
etc.).

The beauty of OO programming is that by the time you start making an object
there can be already almost everything written and tested for you. 

Unfortunately, when writing procedural code, since each program contains
specifics about the solution it presents, there is vastly reduced re-use.

I don't think the tea analogy requires that the other methods be private,
simply that the end user should not have to call each method, as that is
writing the cup of tea procedure. 

In your analogy I noticed that you seem to mix object oriented with object
based. Just to clarify, Object Oriented Programming and Object Based Visual
development are two very different things. When they are combined they are
very, very useful. Bother are very useful by themselves. VisualBasic is
neither. VisualAge for Java is both.

Again, this may be something that you already know, but I just wanted to
clarify, it isn't necessary for an OO language to act based on user
interface events. That just happens to be something common with interactive
processing.


Chris Rehm
Mr.AS400@ibm.net

How often can you afford to be unexpectedly out of business?
Get an AS/400.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---