Hi Nicolas,
The current semantics for both methods and queryOutgoingReferences are quite fine.
As I understand you want to count the amount of references that the code inside a package induces. So, this includes both the extension methods and the defined methods. Why do you see this as a problem?
Cheers, Doru
On 31 Jul 2012, at 16:21, Nicolas Anquetil wrote:
Another MooseChef decision:
aPackage queryOutgoingReferences
returns all the FamixReferences made from aPackage.
this is implemented by taking all methods (self methods) in the package and asking them what reference they make.
And we have FAMIXPackage>>methods ^ self localMethods union: self extensionMethods
So when asking a package what external references it makes, we get references stemming from methods that extend classes of other packages.
We found this while computing a coupling metric for packages.
So the solution would be easy to implement, but we are not sure what is the best solution ?
- we could change FAMIXPackage>>methods (methods belong to the package that owns their class)
- we could change queryOutgoingReferences (references/invocation/accesses stem from the methods in the classes in the package, not from the methods in the package)
- or we could change our metric
nicolas _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."