Care must be taken when loading an edition of an application that declares its variables using toBeLoadedCode if the currently loaded edition declares the same variables using declaration methods. Under these circumstances, all variables are removed from the image if they are managed by declaration methods that have no corresponding declarations in declaration methods in the replacement edition. This happens even if the variables are declared in the replacement edition's toBeLoadedCode because the bindings were in a managed namespace.

Before loading the edition that uses toBeLoadedCode, completely unload the application edition that uses declaration methods. This ensures that all variables declared by toBeLoadedCode are unmanaged. If unloading the application is not feasible, declaration methods should be added to the edition that uses toBeLoadedCode, and toBeLoadedCode should be retained. Such an edition will load properly in both the current version and earlier versions of VAST Platform or IBM Smalltalk.