16 May
2007
16 May
'07
7:07 p.m.
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.
16 May
16 May
7:26 p.m.
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(a)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."
7:27 p.m.
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(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
6430
days inactive
6430
days old
2 comments
3 participants
participants (3)
-
Adrian Kuhn -
Muhammad Bhatti -
Tudor Girba