[Pharo-project] [ANN] 10205
m.rueger at acm.org
Tue Jan 13 16:31:58 EST 2009
On Tue, Jan 13, 2009 at 10:02 PM, Igor Stasenko <siguctua at gmail.com> wrote:
>> Because it loads one package after the other.
>> Usually the right load order fixes the problem, but in this case loading
>> stops working because crucial classes go missing during loading.
> which only shows that code stinks and need further refactorings to
> avoid heavy package interdependencies.
> don't blame the tool :)
In this case it is a problem with how MC treats a class move.
If you load the package first that now includes the class, loading the
other removes the class from the system.
Loading the packages the way round works. After loading the first
package the class is missing, then added by the other package the
class was moved to. Unfortunately in this case the missing classes are
needed for loading packages so you are stuck.
More information about the Pharo-dev