home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.object
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sdd.hp.com!ux1.cso.uiuc.edu!cs.uiuc.edu!johnson
- From: johnson@cs.uiuc.edu (Ralph Johnson)
- Subject: Re: A little glossary for objects
- Message-ID: <Bzz8y7.Jn5@cs.uiuc.edu>
- Organization: University of Illinois, Dept. of Comp. Sci., Urbana, IL
- References: <knight.724948496@cunews> <1992Dec23.151238.3419@Informatik.TU-Muenchen.DE> <1992Dec27.014406.26583@mole-end.matawan.nj.us>
- Date: Mon, 28 Dec 1992 16:10:55 GMT
- Lines: 24
-
- mat@mole-end.matawan.nj.us writes:
-
-
- >In such languages, the use of `sub' and `super' is often confusing, because
- >the subclass is represented by a superstructure on the superclass. (Hence
- >the classic advice to OO'rs moving to C++: ``Don't say `sub' and `super,' say
- >`base' and `derived'.'')
-
- The C++ programmers around here all say "subclass" and "superclass",
- and nobody gets confused. They never use the word "superstructure".
- "Base" and "derived" are perfectly good words, too, but they are no
- better or more natural than "subclass" and "superclass". What is
- important is to be consistent and to avoid introducing too much new
- terminology. One of the problems with the OO field is that each idea
- has several names. This makes it hard for people to communicate with
- each other. Since several different languages are used here, everyone
- uses the terms "subclass" and "superclass" and people can communicate
- with each other easily, even if they are used to using different
- programming languages.
-
- Ralph Johnson -- University of Illinois at Urbana-Champaign
-
-
-
-