Status: New Owner: ---- Labels: Type-Defect Priority-Medium Difficulty-Easy Milestone-4.4
New issue 616 by jannik.l...@gmail.com: cleaning package cycles http://code.google.com/p/moose-technology/issues/detail?id=616
Not sure how we should implement traits but I think that
Traits TDependencyQueries, TScopingEntityQueries, TDependencyQueryResult should have categories (protocol) beginning with '*Famix-Core-MooseChef'
Comment #1 on issue 616 by tudor.gi...@gmail.com: cleaning package cycles http://code.google.com/p/moose-technology/issues/detail?id=616
I do not understand. What is the issue here?
Comment #2 on issue 616 by jannik.l...@gmail.com: cleaning package cycles http://code.google.com/p/moose-technology/issues/detail?id=616
In fact, for now, all methods copied from the traits to the classes are in a protocol named "mooseChef". All these classes are in FAMIX-Core. It makes a dependency from FAMIX-Core to FAMIX-Core-Moosechef.
In my analysis, I do not take into account the Traits, and I am not sure how to take them into account. I do not know if this is a structural issue or not.
Comment #3 on issue 616 by tudor.gi...@gmail.com: cleaning package cycles http://code.google.com/p/moose-technology/issues/detail?id=616
The problem is that Chef should be an extension, but it is not possible with Pharo because we cannot add a Trait as an extension. So the result is that we merged Chef in Famix-Core, but we put it in a sub category.
However, this breaks the convention of one category per package. So, we should simply move the Traits to Famix-Core until we will get some better support for Trait extensions.
Updates: Status: Fixed
Comment #4 on issue 616 by tudor.gi...@gmail.com: cleaning package cycles http://code.google.com/p/moose-technology/issues/detail?id=616
(No comment was entered for this change.)
-
moose-technology＠googlecode.com