Le 10 oct. 2017 à 15:54, Cyril Ferlicot
<cyril.ferlicot(a)gmail.com> a écrit :
On Tue, Oct 10, 2017 at 3:45 PM, Anne Etien <anne.etien(a)univ-lille1.fr> wrote:
No, it does not make sense.
By putting TOODependencyQueries to FAMIXNamedEntity and not FAMIXEntity, the idea was to
query only non association entity. It was the only way to do it.
If you look at the users of TDependencyQueries, it is all the non association entity that
have no name.
If you do the change you suggest, you will be able to ask queryAllIncomingAssociations on
a FAMIXInvocation, what makes no sense.
So the only way to do it is to say that the entity should not inherits from
FAMIXAssociation.
Would it not be less constraining to make FAMIXEntity use
TDependencyQueries and to override #query:with: (and the other query
methods not using this one) to throw an error?
Because now each time we implement an entity that is not named we need
to think to add the trait and we cannot expect all famix entities to
be able to answer to methods like #queryAllIncomingAssociations
I don’t understand the end of the last sentence.
Not so sure, because as it is currently done, FAMIXComment can not answer to method like
queryAllIncomingAssociations, because it is not linked to other entities through any
association just a container relationship that is not an association. It can be the case
of other entities (I have no idea which one).
Anne
Anne
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev
--
Cyril Ferlicot
https://ferlicot.fr
http://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev