On 21 janv. 2011, at 23:00, Stéphane Ducasse wrote:
On Jan 21, 2011, at 10:11 PM, Simon Denier wrote:
On second thought I think you're right.
Or more precisely a ClassExtension (as a subclass of FamixAssociation) should be
from aFamixMethod to aFamixClass
why?
FamixPackages already have methods to retrieve class extension (as well as extended classes).
Now if we want class extensions as first-class entities, I think it's better to take the smallest granularity of representation, to be able to manipulate one class extension separately from another (for example Orion could manipulate extensions one by one). In this case that would based on the extension supported by a FamixMethod and the extended FamixClass.
The other reason I believe in this solution is that it seems to fit nicely with the current work on queries :)