2009/1/13 Michael Rueger <[email protected]>: > 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 >> enabled. > > 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 :)
> Michael > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
