Daniel,

Comments below.

On 27/03/2014 5:59 PM, Daniel Tahin wrote:
> Hello,
>
> for an EClass in Ecore, more than one Superclasses can be specified. I
> would like to ask, if this multiple inheritance is exactly the same,
> as for C++? (Is there things, i should consider if i translate a class
> with multiple superclasses in a language other than Java or C++?)
Yes and no. We try to make it mostly behave the same, but in the end,
there are implementation details that make it not exactly the same. In
particular, the first super EClass of an EClass is special because the
implementation class of that super EClass will be extended by the
implementation class of the EClass. In terms of dynamic models, that
means the first non-dynamic EClass recursively reachable via the first
super EClass in the inheritance chain will be instantiated as the base
implementation class; as a consequence, you can't dynamically extend an
abstract non-dynamic EClass because its implementation class will also
be abstract and you can't instantiate an abstract class in Java. In
terms of generated models, that means all the additional super EClasses
are like mix-ins and those interfaces need to be reimplemented in the
derived class; as a consequence, it's best order the super EClasses so
that the largest, most significant implementation is reused. Of course
the generator will happily generate a full implementation for you no
matter the order, but if there are hand written changes, those will need
to be hand duplicated in the mix-in case.
>
> Thank you in advance,
> Daniel
>