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=0.6 required=5.0 tests=BAYES_20,INVALID_MSGID,
	T_FILL_THIS_FORM_SHORT autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,9af30ff1a54d60cf,start
X-Google-Attributes: gid103376,public
From: "W. Wesley Groleau (Wes)" <wwgrol@PSESERV3.FW.HAC.COM>
Subject: Re: Ada 95 OOP questions
Date: 1996/08/14
Message-ID: <9608141717.AA08650@most>#1/1
X-Deja-AN: 174689168
sender: Ada programming language <INFO-ADA@LISTSERV.NODAK.EDU>
comments: To: info-ada%listserv.nodak.edu@emcee.com
mailer: Elm [revision: 70.85]
newsgroups: comp.lang.ada
Date: 1996-08-14T00:00:00+00:00
List-Id: <comp.lang.ada>


I offer a compromise to anyone who wants Ada to be more obvious about
the relationship between an object/class/type and its methods/operations.

If you get a warm fuzzy from

    class Person
    {
       Eat();
       Walk();
       Talk();
    }

perhaps you would feel good about

    protected Person is
       entry     Eat;
       procedure Walk ( To    : in Location );
       function  Talk ( About : Subject ) return Words;
    private
       Name : Name_Type;
    end Person;

And you can even put persons in arrays, record fields, or linked lists.
You can pass them as parameters, and each Person knows his/her name without
having to call it "my.Name"

---------------------------------------------------------------------------
W. Wesley Groleau (Wes)                                Office: 219-429-4923
Hughes Defense Communications (MS 10-40)                 Home: 219-471-7206
Fort Wayne,  IN   46808                  (Unix): wwgrol@pseserv3.fw.hac.com
---------------------------------------------------------------------------