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: 103376,e5eb8ca5dcea2827,start X-Google-Attributes: gid103376,public From: "Shawn M. Root" Subject: Ada OO Mechanism Date: 1999/05/20 Message-ID: <7i05aq$rgl$1@news.orbitworld.net>#1/1 X-Deja-AN: 479909211 Organization: OrbitWorld Network, Inc. X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Newsgroups: comp.lang.ada Date: 1999-05-20T00:00:00+00:00 List-Id: Greetings, I've been lurking on this newsgroup for about a year now and would first like to thank all of you who contribute to this group regularly for your very interesting and informative discussions. These discussions have led me to a better, though still very limited, understanding of Ada. I would like to ask a question, however. In a recent thread entitled "A question for my personal knowledge" some people were saying that the Ada OO mechanism was counterintuitive. I tend to agree. This concern was dismissed by others as being merely "syntactic sugar", and claims were made that the Ada mechanism is actually easier to use than the C++ style. These arguments seemed misplaced to me. I thought that one of the goals of Ada was to focus on the reader of the code, not the writer. Therefore if this "syntactic sugar" makes code easier to understand, then it would be a good thing, right? Perhaps I've missed the point, but it seems like a Class construct would fit in well with the Ada way of doing things. It seems like a logical evolution from a package, to a generic package, to a class. The syntax would even be similar since (at least where I work) use clauses are rarely used. We write Package_Name.Procedure; so what's wrong with Class_Name.Method; Maybe I just don't understand the issues. I would appreciate any help in making this clear. Thanks. -- Shawn M. Root