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.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,7251fa99aab97e06 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1993-03-10 13:10:15 PST Newsgroups: comp.lang.ada Path: sparky!uunet!widget!jgg From: jgg@evb.com (John Goodsen) Subject: Re: Ichibah flames, and flames out over, Ada 9X Message-ID: <1993Mar10.203901.6411@evb.com> Organization: EVB Software Engineering, Inc. Date: Wed, 10 Mar 1993 20:39:01 GMT Date: 1993-03-10T20:39:01+00:00 List-Id: wellerd@ajpo.sei.cmu.edu (David Weller) writes: >Tucker would be quick to point out that the word "record" is also >an implementation detail, but that it's become generally accepted >in the programming domain. This is irrelevant to the class vs. tagged type discussion. Or is it? "class" is generally accepted in the OO programming domain. Tagged Type ? really not even known in the OO programming domain. >Frankly, I don't care for the word >"tagged" either, but "class" doesn't fit in its place. > By what measurement? C++ syntax? Again, if you want to make an impact against markets like the C++ market, you need to at least speak the language. Change the semantics for technical superiority, but you'll never get the OO message out using terminology that the OO community doesn't (for the most part) understand, namely "tagged types". >One other thing that's bothered me -- why are we raising such a fuss >about the word "tagged" to mean "this record may have it's state >description extended"? Perhaps we're being pedantic? The whole argument for class vs. tagged type is based solely upon the need for Ada 9X to gain support as an OO language. This is not pedantic. It is realistic awareness of the programming community and how to grow a business centered on Ada technology. -- John Goodsen Software Process & Environments EVB Software Engineering jgg@evb.com