ptx/C++ Runtime V5.2.5 Release Notes

ptx®/C++ Runtime V5.2.5 consists of the shared versions of the ptx/C++ libraries. These are equivalent to the static versions of the libraries that are part of the corresponding release of ptx/C++.

The shared libraries are in a separate product to allow Independent Software Vendors (ISVs) to build products that use the shared C++ libraries without requiring their customers to license the ptx/C++ product. If you are using ptx/C++ in a development environment, you must install both ptx/C++ and ptx/C++ Runtime. For information about the functionality of ptx/C++ V5.2.5 and the ptx/C++ libraries, refer to the ptx/C++ V5.2.5 Release Notes.


ATTENTION

There is no shared library version of RogueWave® Tools.h++® Version 8.



Software Compatibility

The ptx/C++ Runtime product is compatible with ptx/C++ V5.2.5 and runs on DYNIX/ptx® V4.5.x or DYNIX/ptx V4.6.x.


Libraries with Thread Support

The following libraries in ptx/C++ Runtime are used by applications that are built on DYNIX/ptx V4.5 and run on either DYNIX/ptx V4.5 or DYNIX/ptx V4.6 or that are built on DYNIX/ptx V4.6 and run on DYNIX/ptx V4.6:

/usr/lib/libc++.so.2
C++ standard library (ANSI compatible)
/usr/lib/libcomplex.so.3
Complex library (cfront compatible)
/usr/lib/libec++.so.2
C++ runtime support (cfront compatible)
/usr/lib/librwtool.so.7
Rogue Wave Tools.h++ Version 7 (cfront compatible)
/usr/lib/libstd.so.3
Streams library (cfront compatible)

Libraries Without Thread Support

The following libraries in ptx/C++ Runtime are used by applications that are built on DYNIX/ptx V4.4 and run on either DYNIX/ptx V4.5 or DYNIX/ptx V4.6:

/usr/lib/libc++.so.02
/usr/lib/libcomplex.so.03
/usr/lib/libec++.so.02
/usr/lib/librwtool.so.07
/usr/lib/libstd.so.03

Install ptx/C++ Runtime

ptx/C++ Runtime V5.2.5 is installed on DYNIX/ptx V4.5.x or V4.6.x using the standard ptx/INSTALL procedure and does not require a license. For installation instructions, refer to the DYNIX/ptx V4.5.2 and Layered Products Software Installation Release Notes or the DYNIX/ptx V4.6.0 and Layered Products Software Installation Release Notes as applicable.

ptx/C++ Runtime V5.2.5 is distributed on both the "DYNIX/ptx V4.5.2 Operating System and Layered Products, Volume 1" CD-ROM and the "DYNIX/ptx V4.6.0 Operating System and Layered Products, Volume 1" CD-ROM.

If you are also installing ptx/C++, then you should install the release of ptx/C++ Runtime that has the same version number. If you are not installing ptx/C++ on your system but need ptx/C++ Runtime for use with another product, then you should install a version that is at least as recent as the one required by that product.


Fixed Problems in ptx/C++ Runtime V5.2.5

The following list contains the problem reports fixed in ptx/C++ V5.2.5. The first number shown in bold font is the SPTS problem report number. The second number shown in brackets is the EPC problem report number.

249652 [4259]
The Tools.h++ class RWTime had problems if used in a shared object; it could cause times to be shown in GMT instead of the local time zone. This problem was previously fixed in Fastpatch 252265 against ptx/C++ V5.2.3.
252094 [4763]
The compiler's exception handling support caused a runtime abort in the library function __ex_free() for code that was compiled with the -O1 or -O option to c++.
252123 [4774]
The compiler's exception handling support failed to generate a call to the destructor for the base class of a thrown object of a derived class.
252625 [4896]
The member function strstreambuf::overflow() had a bad call to memset(), which caused a runtime segmentation violation.
252713 [4956]
Some string support functions in Tools.h++ incorrectly allocated memory using new[], but then freed it using delete rather than delete[]. This caused extraneous messages from memory leak tools, but did not cause C++ applications to run incorrectly.
253452 [5012]
The constructor for the class ostrstream wrote one byte past the end of the buffer. This could cause a segmentation violation at run-time.
253548 [5038]
The default thousands separator for numbers in the "C" locale should be nothing, but the numpunct<charT> functions for char and wchar_t returned a comma.