HP aC++ A.03.85 Release Notes

HP aC++ Release Notes
New Features in Version A.03.30
Chapter 1 47
New Features in Version A.03.30
New features in HP aC++ version A.03.30 are listed below.
• Standard C++ Library 2.0 Base on the New Rogue Wave SL 2.0
• Easier User of Threads with -mt
• Partial Support for ANSI C Compiler
Standard C++ Library 2.0 Base on the New Rogue Wave SL 2.0
The new -AA command line option enables use of the new 2.0 Standard C++ Library, which
includes the new standard conforming (templatized) iostream library. This is the first release
of the 2.0 library. It conforms to the ISO C++ standard.
The 2.0 library is a new addition to the HP C++ runtime is not compatible with the version
1.2.1 Standard C++ Library previously bundled with HP aC++. HP aC++ will continue
support for standard C++ library 1.2.1 without name or location change. Customers should
not notice any change when -AA is not used. However, the 1.2.1 library is deprecated and will
be replaced by the new library eventually.
If you wish to use the new 2.0 library, you must use the -AA option consistently to compile and
link all translation units. Mixing object files within an executable is not supported.
The version of the 2.0 Standard C++ library (libstd_v2) included in this release is
incompatible with the previous versions of the same library. Using the -AA option and the new
2.0 library creates a binary incompatibility with any other applications or libraries compiled
with the -AA option under the previous version of the aC++ product.
In order to use the new 2.0 library, you must recompile using the -AA option and you may need
to apply a runtime and/or header file patch appropriate to your operating system (see list
below). You do not need to install the header file patch if you use the A.03.30 compiler.The
header file patches are needed for A.03.27, A.03.26, A.03.25, and A.01.27.
You can avoid the binary incompatibility simply by not using the -AA option and foregoing use
of the 2.0 library. If you don’t use -AA, you should still install the patches. If you do use -AA
and you are on A.03.30, the header file patches are included in A.03.30 but you must still
install the runtime patches. Then you must recompile and relink any previous -AA
application.
HP does not take the creation of binary incompatibilities lightly. When one is created, it is
only after a careful consideration of options and ramifications. Our customers want to be able
to use the new 2.0 library. Doing this also ensures compatibility with the Multibyte Support