Binary and Run-Time Interoperability with Previous Releases

DLLs, executable files, and libraries created in previous releases can coexist with this release. The changes that are required and the restrictions that apply are described in the topics under Related Tasks.

There are some restrictions to interoperability because static data and functions are contained in each run time. Consider an executable file created with this release of VisualAge, and a DLL created with VisualAge for C++ Version 3.5. In both cases, a shared run-time option was specified when they were created. The run-time library is not statically linked into the .exe or .dll. Since both this release of the product and the previous release have their own static data, any interaction between the .exe or .dll that relies on the static data in their respective run times cause unpredictable results. For example, a function in the .dll is called from a catch block in the .exe, and the function in the .dll tries to re-throw the exception. Since the exception handling information is stored in the run-time library associated with the .exe, the run time associated with the .dll cannot re-throw the exception.



Use DLLs and Executable Files Created in Previous VisualAge C++ Releases


C and C++ Binary and Run-Time Interoperability with Previous Releases
Object Files Created in Previous VisualAge C++ Releases