On Mar 21, 2010, at 8:40 PM, Adrian Lienhard wrote: > On Mar 21, 2010, at 19:50 , Marcus Denker wrote: > >> >> Yes... #isInMemory is clearly not needed anymore. > > Well... it is needed for the swapping out of classes. If we remove > #isInMemory, we should also remove the whole image segment stub mechanism > because it becomes useless without the isInMemory protection. >
But was this ever working? Was this ever *used* the last 10 years? Are actually all cases covered? So are there enough #isInmemory checks to not end up with loading everything anyways? We already removed the *gently variants for iterating over subclasses, for example. or the "ifPresentAndInMemory" things.... > I would like to keep that working and extract it with the image segments code > into an external package. How to do this cleanly is an interesting question, > though... > I think we should ask the question: Do we intent to *use* this mechanism *at all* the next 5 years? -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
