On 9 déc. 2010, at 18:50, Sean P. DeNigris wrote: > * What if ClassFactoryForTestCase used the separate-SystemDictionary > approach? Wouldn't you only need to clean up the logs and the classes would > get gc-ed (even if cleanup was never called)?
> * Is my OP correct that it is safe to do what I was doing i.e. no effect to > the system (except maybe the doit in the changes)? (I may have another > application for it) Your usage of the classbuilder looks sound. But, deleting your environment is not enough, at least not enough to ensure the deletion of your classes. You need : -to delete all references to classes for your environment from their superclasses. This is part of what is performed by the obsolete message. -ensure that no instance of classes of your environement is referenced from root objects (e.g. default environment). Cause a class can't be GCed if its instances are still accessible. Noury
