Hello all,
while extracting the inheritance definition of a class, this question poped up in my mind: how do we specify multiple child classes for a class? Do we create a new InheritanceDefinition for each one of them, which seems to be the case with existing MSE files? For example X <- Y <- A,Z (X is the base class, Y inherits from X, A,Z inherit from Y) In this case, inheritancedefinition parameter for Y will be (format *Class* for elaboration)
(FAMIX.InheritanceDefinition (id: 6) (superclass (idref: 1 *X*)) (subclass (idref: 3 *A*)) )
(FAMIX.InheritanceDefinition (id: 7) (superclass (idref: 1 *X*)) (subclass (idref: 4 *Z*)) )
thanx Usman
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
Hi Usman,
Indeed, you have to create one InheritanceDefinition for each inheritance relationship.
In general, in the FAMIX meta-model, you would have to build one object for each relationship.
Cheers, Doru
On May 16, 2007, at 7:07 PM, Muhammad Bhatti wrote:
Hello all,
while extracting the inheritance definition of a class, this question poped up in my mind: how do we specify multiple child classes for a class? Do we create a new InheritanceDefinition for each one of them, which seems to be the case with existing MSE files? For example X <- Y <- A,Z (X is the base class, Y inherits from X, A,Z inherit from Y) In this case, inheritancedefinition parameter for Y will be (format *Class* for elaboration)
(FAMIX.InheritanceDefinition (id: 6) (superclass (idref: 1 *X*)) (subclass (idref: 3 *A*)) )
(FAMIX.InheritanceDefinition (id: 7) (superclass (idref: 1 *X*)) (subclass (idref: 4 *Z*)) )
thanx Usman
This message was sent using IMP, the Internet Messaging Program.
-- Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Tudor Girba www.iam.unibe.ch/~girba www.iam.unibe.ch/~girba/blog/
"Problem solving efficiency grows with the abstractness level of problem understanding."
Hello Usman, the inhertance definition is a relation (cRs) between a class (c) and its direct superclass (s), ie for your example
x <-- y <-- a, z
there would be three FAMIX.InheritanceDefinition elements
yRx, aRy, zRy
Does this answer your question?
cheers, AA
On 16 May 2007, at 19:07 , Muhammad Bhatti wrote:
Hello all,
while extracting the inheritance definition of a class, this question poped up in my mind: how do we specify multiple child classes for a class? Do we create a new InheritanceDefinition for each one of them, which seems to be the case with existing MSE files? For example X <- Y <- A,Z (X is the base class, Y inherits from X, A,Z inherit from Y) In this case, inheritancedefinition parameter for Y will be (format *Class* for elaboration)
(FAMIX.InheritanceDefinition (id: 6) (superclass (idref: 1 *X*)) (subclass (idref: 3 *A*)) )
(FAMIX.InheritanceDefinition (id: 7) (superclass (idref: 1 *X*)) (subclass (idref: 4 *Z*)) )
thanx Usman
This message was sent using IMP, the Internet Messaging Program.
-- Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Adrian Kuhn -
Muhammad Bhatti -
Tudor Girba