[Pharo-project] [ANN] 10205
siguctua at gmail.com
Tue Jan 13 16:02:04 EST 2009
2009/1/13 Michael Rueger <m.rueger at acm.org>:
> Keith Hodges wrote:
>> Michael Rueger wrote:
>> I dont see that the following follows.
>>> "and thus needs to be loaded from a configuration map."
>> Option 1, Atomic loading. Available in MC1.5/6 as an option that can be
> hmm, we don't have MC 1.5 in Pharo yet, or did I miss that?
>>> I tried loadTogether:merge: but that still ends up with classes missing
>>> in the image.
>> Might be worth finding out why.
> 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 :)
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
Igor Stasenko AKA sig.
More information about the Pharo-dev