I am designing an iterator, but in this case I will be iterating APP files in different locations and with different pedigree. In this case, I will certainly be encountering situations where both my iterator EXE and the visited APP file will have some of the same utility classes, possibly not of identical versions. I have a few questions, in case anyone has gone down this path before:

1) If a certain class "myClass" is in memory via a previous SET PROCEDURE, and then I issue a different SET PROCEDURE ADDITIVE command where the new procedure also has a class named "myClass", do I have any guarantee of which class will be used when I then CREATE("myClass")?

2) After visiting any specific APP, I want to release any classes that app put into memory. Assuming all objects have been released, my plan was to save the current state of SET("PROCEDURE") before visiting the APP, and then restoring that after leaving. (Various other environment restoring will also be done.) Does this sound like a stragegy that would release me of the effects of visiting the first APP, thus allowing the EXE to visit the next APP without cross-talk, etc?

Any advice or war stories appreciated.

-- Randy