Implementation of isPackage, isClass...

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Implementation of isPackage, isClass...

Anne Etien
Hi,

The isPackage method is implemented only in FAMIXNamedEntity (and obviously in FAMIXPackage).
The isClass method is implemented only in FAMIXSourcedEntity (and obviously in FAMIXClass).
The isAttribute method is implemented only in FAMIXStructuralEntity (and obviously in FAMIXAttribute).
The isMethod method is not implemented…

Why not harmonizing this and defining all these methods in FAMIXEntity?

In fact, I am working with Nicolas Anquetil on the diff of models. I would like to create an Orion action for each change. Thus, if a class is added between version n and version n+1, I would like to instantiate an AddClass operator. And so on for each change. So I need to know the type of the FAMIXEntity on which the change occurred. Using these methods would be tidier than using isKindOf: method.

Please let me know if such implementations make sense for you or not.

Anne
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Implementation of isPackage, isClass...

Tudor Girba-2
It makes sense. Go for it.

Doru


On Tue, Jul 2, 2013 at 5:43 PM, Anne Etien <[hidden email]> wrote:
Hi,

The isPackage method is implemented only in FAMIXNamedEntity (and obviously in FAMIXPackage).
The isClass method is implemented only in FAMIXSourcedEntity (and obviously in FAMIXClass).
The isAttribute method is implemented only in FAMIXStructuralEntity (and obviously in FAMIXAttribute).
The isMethod method is not implemented…

Why not harmonizing this and defining all these methods in FAMIXEntity?

In fact, I am working with Nicolas Anquetil on the diff of models. I would like to create an Orion action for each change. Thus, if a class is added between version n and version n+1, I would like to instantiate an AddClass operator. And so on for each change. So I need to know the type of the FAMIXEntity on which the change occurred. Using these methods would be tidier than using isKindOf: method.

Please let me know if such implementations make sense for you or not.

Anne
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev