Article View: comp.lang.misc
Article #5859object oriented design decision
From: Daniel B Hankins
Date: Sat, 29 Oct 1988 13:59
Date: Sat, 29 Oct 1988 13:59
30 lines
1107 bytes
1107 bytes
An addendum to my previous posting: In the case where one wishes to inherit everything from a parent save a few individual message handlers or local variables, one might want something like: class X; superclasses A, B, C; from A discard Y; . . . This would allow even more flexibility in inheritance. Another alternative is to handle name importing the way Modula-2 does - if an individual name is wanted, one specifies from X inherit Y but if complete inheritance is wanted, inherit X is used, and references to names in X must be prefixed with their class name, as in: tell X.K move-arm Any ideas or suggestions? Dan Hankins
Technical Details
Message-ID:
<10633@cup.portal.com>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!watmath!clyde!mcdchg!chinet!att!osu-cis!tut.cis.ohio-state.edu!rutgers!apple!bionet!agate!labrea!decwrl!sun!pitstop!sundc!seismo!uunet!portal!cup.portal.com!dan-hankinsShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!watmath!clyde!mcdchg!chinet!att!osu-cis!tut.cis.ohio-state.edu!rutgers!apple!bionet!agate!labrea!decwrl!sun!pitstop!sundc!seismo!uunet!portal!cup.portal.com!dan-hankins From: dan-hankins@cup.portal.com (Daniel B Hankins) Newsgroups: comp.lang.misc Subject: object oriented design decision Message-ID: <10633@cup.portal.com> Date: 29 Oct 88 13:59:25 GMT Organization: The Portal System (TM) Lines: 30