Equivalence relation on FAMIX entities

> Hi all,
>
> I want to implement equivalence relation on FAMIX entities.
> For example, methods m1, m2 are equivalent if they have the same name,
> same signature and their classes have the same name.
> Any idea to introduce these relations in a customizable way in FAMIX ?
> I guess I have to introduce a new meta-model in the FAMIX family ?
>
> Regards,
> --
> Serge Stinckwich
> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
> http://www.doesnotunderstand.org/
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

> We defined several methods:
> - a isVersion: b
> a and b have the same class, the same name and their owners are isVersion:
> one of the other
>
> - a equalNoName: b
> similar to isVersion, but we allow them to have different names (allows
> renaming)
>
> - a equalNoOwner: b
> similar to isVersion, but we allow them to have different owners (allows
> moving)

> Dear Nicolas,
>
> On Thu, Jun 13, 2013 at 12:47 PM, Nicolas Anquetil
> <[hidden email]> wrote:
>>
>> I am not sure why you want to do this in the metamodel?
>>
>> May be there is something I am not understanding here.
>
> Yes you are right, we don't need to add equivalence relations in the
> meta-model, we just need
> to extend the existing FAMIX meta-model with some specific queries.
>
>> Anyway, with Anne Etien, we are implementing something to compare two models
>> and find if two entities model the same thing (typically two FamixMethods
>> modelling the same concrete method in two versions of a software)
>
> Yes, this is very similar to what we want to do actually with a
> colleague from Paris 6 University :-)
> Be able to test if 2 entities of two different models are equivalent or not.
>
>> We defined several methods:
>> - a isVersion: b
>> a and b have the same class, the same name and their owners are isVersion:
>> one of the other
>>
>> - a equalNoName: b
>> similar to isVersion, but we allow them to have different names (allows
>> renaming)
>>
>> - a equalNoOwner: b
>> similar to isVersion, but we allow them to have different owners (allows
>> moving)
>
> I would like to implement something like:
>
> method1 isEquivalentTo: method2 withRelation: aBlock
>
> where the equivalence relation is defined in aBlock.
>
> Regards,
> --
> Serge Stinckwich
> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
> http://www.doesnotunderstand.org/
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev