search

squeak-smalltalk / squeak-object-memory

Issues and assets related to the Squeak object memory.
https://bugs.squeak.org
MIT License
11 stars 1 forks source link

Document `aggressive` parameter in class-side `cleanUp:` #96

Open LinqLover opened 10 months ago

LinqLover commented 10 months ago

SmalltalkImage>>#cleanUp:except: says:

"Clean up. When aggressive is true, this will destroy projects, change sets, etc. Leave out any classes specifically listed in exclusions." "Smalltalk cleanUp: true except: {Project. ChangeSet}"

However, this leaves a lot of room for interpretation: Should I remove any user data (e.g., caches, logs, settings) in my applications if aggressive is false? I assume yes for caches, but I am not sure about the others.

Maybe we can find a decision for such cases and document this in the comment cited above.

timrowledge commented 10 months ago

I would argue that an aggressive cleanup should leave the image in a state ready for distribution to other users, and as such pretty much anything cached ought to be flushed. Settings should end up in a state suited to distribution - ie no personal info but possibly setting for a specific application if that is what is being distributed.

tim

tim Rowledge; @.***; http://www.rowledge.org/tim Strange OpCodes: JUM: Jeer at User's Mistake