This is on purpose :) We plan to have Smalltalk -> SmalltalkImage current soon (after all the years I have been waiting for it to happen this is good to see it happening in squeak It was not top priority for pharo but on the huge todo so now we will do it). Stef
MyClass class>>cleanUp: aggressive This (class-side) method is called with an argument that indicates whether to do aggressive, i.e., potentially destructive cleanup. Doing aggressive cleanup will delete projects, change sets, uni-classes and more. Gentle cleanup is expected to only flush transient caches. If your class only has gentle cleanup you can simply implement
MyClass class>>cleanUp
By default #cleanUp: delegates to this method (similar to startUp/startUp: and shutDown/shutDown:). You can run cleanup by executing:
Smalltalk cleanUp. Smalltalk cleanUp: true.
It seems there is a problem as cleanUp or cleanUp: are implemented in SmalltalkImage but not in SystemDictionary...so evaluating
Smalltalk cleanUp. Smalltalk cleanUp: true.
gives a DNU.
Another question....wouldn't be a good idea to add at least a "Smalltalk cleanUp. " in ScriptLoader >> cleanUpForRelease ??? or similar....
Cheers
Mraiano
Thanks luc for your analysis. After lunch in hot room is never that good for my brain :)
Stef _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project