On Jan 23, 2010, at 1:13 AM, Martin McClure wrote: > Stéphane Ducasse wrote: >> hi guys >> >> the more I read about imageSegments the more I would like to remove them (or >> to package them >> carefully - not sure that this is possible) and may be add a new class to >> just have one simple way of invoking the save (but not swapping back in) >> >> I think that mariano diving into them is a great phd exercise but on the >> long run >> I see it as a brittle mechanism. > > ImageSegments currently have some problems, but are useful. > > Rather than remove them, I'd like to see them evolve to be > better-implemented as people have energy to work on them. Me too this was the original plan.
> If necessary, > put a "not for the faint of heart" sign on them in the meantime. clearly :) This is why mariano started to package them better (even if their influence is creeping in lot of dark corners). Now one of the difficult problem with imagesegment is that as soon as you have a out (of the root graph) pointer pointing in an object in the root graph then this subgraph will not be saved. This means that as soon as you have a closures, session, thread.... holding a ref to any subgrpah objects you can save half of your data. This is why netstyle fork and do brain surgery on the image then save and throw away the image after saving it. Stef _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
