Hi,
MooseQuery has been integrated in the Moose 6.0 (Thanks Vincent!). Normally, it works on
Pharo and Java Famix model. If you want to be able to use MooseQuery on any other
language, you have to add new pragmas in the ‘annotations' class method of the famix
entities.
Please notice that currently, as previously announced, MooseQuery has not the same
behavior than MooseChef concerning the method extensions.
Considering classA having a method methodA1 calling a method methodBExt1 that extends
classB.
classB is defined in pckgB and its extension method by pckgC.
Considering the two following requests:
1. classA queryOutgoingInvocation atClassScope atPackageScope
2. classA queryOutgoingInvocation atPackageScope
To the first query, MooseChef and MooseQuery answer the same: pckgB
To the second query, MooseChef answers pckgC and MooseQuery answers pckgB and pckgC.
After discussion with some people here in Lille, it is difficult to remain generic (as it
is the purpose of MooseQuery) and to manage this specific case where the owner of a method
can be either a package or a class.
I tried to lock Stéphane in his office and force him to discuss with me about this issue
and have a look at the code, but until now he succeeds to escape ;o)
If you have any question or feedback please feel free to share.
Anne