1.4 Backward Compatibility

NOTE: In addition to this Build Guide, please consult the readme file for the latest information on compatibility.

If you plan to use Tools.h++ Professional with applications that used a pre-SPM version of Net.h++, Inter.Net.h++, or ORBstreams.h++, you must change the workspace include path and the link library name in all relevant makefiles or IDE projects. If you owned a pre-SPM version of one of these products, be sure to read the SPM online help topic "Compatibility Issues."

If you plan to use Tools.h++ Professional with applications that used a version of one of the above products from a pre-November 1997 SPM CD, you might need to change the workspace include path in all relevant makefiles or IDE projects. Check the SPM online help topic on compatibility issues for more information.

Otherwise, you should not need to change your existing applications for them to work with Tools.h++ Professional. The libraries generated for Tools.h++ Professional conform to the same naming conventions as the libraries for the products incorporated into Tools.h++ Professional. Also, although SPM places the header files for the Tools.h++ Professional classes in a different location from the location for the earlier products, Tools.h++ Professional provides header files in the old locations with #include statements that point to the new header files.

NOTE: These header files in the old locations, included now for backward compatibility, will eventually disappear for a future release of Tools.h++ Professional. You are encouraged to update your existing applications to use the new location for the header files (see Section 2.3).