For sure, I can :), But maybe you want a dsm to see cycles ?
To do simple, isAbstract is defined in Famix-Core, but all other isSomething are defined in FamixExtensions. It seems to be correct to move it with other test methods.
For the ret, maybe we could do this:
extend method>> Smalltalk::FAMIXPackage.definedMethods() in Famix-Extensions.
it is an alias of self methods, it should be in Famix-Implementations
extend method>> Smalltalk::FAMIXPackage.localClasses() in Famix-Extensions.
it is an alias of self classes, it should be in Famix-Implementations
extend method>> Smalltalk::FAMIXPackage.extendedClasses() in Famix-Extensions. extend method>> Smalltalk::FAMIXPackage.extendedClassesGroup() in Famix-Extensions. extend method>> Smalltalk::FAMIXPackage.extensionClasses() in Famix-Extensions. extend method>> Smalltalk::FAMIXPackage.extensionClassesGroup() in Famix-Extensions. extend method>> Smalltalk::FAMIXPackage.extensionMethods() in Famix-Extensions. extend method>> Smalltalk::FAMIXPackage.localMethods() in Famix-Extensions. extend method>> Smalltalk::FAMIXPackage.localClassesGroup() in Famix-Extensions.
These methods are used by Cook, which is in Famix-Extension now. But I will try something else.
Cheers, Jannik
On Feb 17, 2010, at 14:40 , Simon Denier wrote:
Can you provide more incentive about those methods? Why do they create a cycle. And if they create some, perhaps their implementation needs to be changed.
On 17 févr. 2010, at 13:46, Laval Jannik wrote:
extend method>> Smalltalk::FAMIXNamedEntity.isAbstract() in Famix-Extensions. extend method>> Smalltalk::FAMIXNamedEntity.isAbstract:(Object) in Famix-Extensions. extend method>> Smalltalk::FAMIXClass.isAbstract() in Famix-Extensions.
=====
Is it ok for you ?
Cheers Jannik
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev