Hi Jannik,

Indeed if we look only at the picture, it does not make much sense not to combine the two.

But, FAMIX is not just a simple meta-model, but it is the core that is supposed to be extended. For example, for Pharo we will also have FAMIXTrait, and this will be subclass of FAMIXType. Or in Java, we will have FAMIXInterface that is subclass of FAMIXType.

That is why we need both :).

Cheers, Doru

On 1 Apr 2009, at 10:26, Laval Jannik wrote:

Hi all,

What is the meaning of FAMIXType ? I know its subclass is FAMIXClass, but why don't we merge them ?

In FAMIXMethod, the variable parentClass has been changed in parentType. I think this is less clear.

The problem is that I don't see what is FAMIXType :)

Thanks for your help.

Cheers

Jannik Laval

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com

"We cannot reach the flow of things unless we let go."

For me, the difference comes from the instantiation part: classes have a type and can be instantiated, whereas types can not be instantianted (at least in mainstream OO languages). FAMIXType can represent pure abstract classes like Java interfaces.

However, with respect to this I feel uncomfortable with FAMIXType>>attributes

Renaming parentClass -> parentType is for unambiguity purpose (since parentClass points to a FAMIXType anyway)

PS: I see that Doru was faster

On 1 avr. 09, at 10:26, Laval Jannik wrote:

Hi all,

What is the meaning of FAMIXType ? I know its subclass is FAMIXClass, but why don't we merge them ?

In FAMIXMethod, the variable parentClass has been changed in parentType. I think this is less clear.

The problem is that I don't see what is FAMIXType :)

Thanks for your help.

Cheers

Jannik Laval

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- Simon