Yes of course. Now since only a subpart of the system was using it it means that imageSegment are most of the time reloaded. So this is clearly a neat idea but not fully working.
Stef On Jan 17, 2010, at 10:27 PM, John M McIntosh wrote: > I think you'll find it's documented in the class > ImageSegmentRootStub > > It's all tied up in image segments, projects, etoys and the like, so in the > past an attempt to ensure > that objects (classes) that were bundled up and stuffed into an image segment > aren't faulted back in > unless you really mean it... > > users of this are interesting, see for example > Dictionary>>at:ifPresentAndInMemory: > > On 2010-01-17, at 1:10 PM, Stéphane Ducasse wrote: > >> isInMemory > > -- > =========================================================================== > John M. McIntosh <[email protected]> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
