[Pharo-dev] [pharo-project/pharo-core] 4021f3: 30523

Tudor Girba tudor at tudorgirba.com
Fri Oct 25 09:31:23 EDT 2013

I agree with this. In particular, the configuration classes offer extra
information that can be used by smart browsers. We need them.


On Fri, Oct 25, 2013 at 3:18 PM, Christophe Demarey <
Christophe.Demarey at inria.fr> wrote:

> Why do we need to remove configurations of projects loaded into the image?
> I would say the opposite: all projects in the image should have their
> configuration loaded. It is part of the project.
> Le 25 oct. 2013 à 14:00, GitHub a écrit :
> > 12005 unload BaselineOfFileTree, BaselineOfMetacello
> >       https://pharo.fogbugz.com/f/cases/12005


"Every thing has its own flow"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131025/f388cdf8/attachment-0002.html>

More information about the Pharo-dev mailing list