Subject: Re: class dictionaries and super classes
From: Karl Lieberherr (firstname.lastname@example.org)
Date: Fri Dec 08 2000 - 11:52:48 EST
>From email@example.com Thu Dec 7 19:30:22 2000
>Date: Thu, 7 Dec 2000 19:30:20 -0500 (EST)
>From: "Brendan M. Coffey" <firstname.lastname@example.org>
>To: Karl Lieberherr <email@example.com>
>cc: Brian Vincenzo Mollo <firstname.lastname@example.org>
>Subject: class dictionaries and super classes
>Brian and I have two questions:
>1) Which CD file should all of our check methods be robust against?
>the sem-check.cd file (the really huge one) is structured completely
>differently from many of the other class dictionaries that are
>"circulating" among the class, such as the scs.cd file in
Use the one in:
which is actually the same as the one in
>2) We are having the following problem in implementing the cyclic
>inheritance check: how can we traverse from a class to its
>superclass(es)? There appears to be no reference to a parent in most
>of the class dicitonaries people are working with. Further, should the
>cyclic inheritance check assume that there is no multiple inheritance?
>If not, the problem becomes significantly more difficult.
>If you look in Bob's (turacma's) directory (we certainly have), he uses
>a class dictionary that has been subtly modified to contain some
>references to superclass structures of his own invention. Is this the
>way we should attack it--by modifying the class dictionary itself?
This is quite typical that you add more structure to your classes
during the implementation. It is a good idea to store for each class
its super classes and these links can be set by a traversal through
the subclasses of all super classes.
Before you check the inheritance cycle rule, it is good to check
the multiple inheritance rule to simplify the checking of the
inheritance cycle rule.
>Brendan & Brian
-- Karl L.
This archive was generated by hypermail 2b28 : Fri Dec 08 2000 - 11:53:10 EST