This manual is a supplement to the Threads.h++ User's Guide. Its purpose is to provide information about the use and implementation of Threads.h++ in the following environments:
IBM AIX, v4.3
IBM xlC C++ Compiler, v3.6.6
IBM POSIX 1003.1c (Draft 10) Thread API
Hewlett-Packard HP-UX, v10.20
HP aCC C++ Compiler, A.01.21
HP OSF/DCE Thread API
Hewlett-Packard HP-UX, v11.00
HP aCC C++ Compiler, A.03.13
HP OSF/DCE Thread API
POSIX 1003.1c Thread API
SGI IRIX64, v6.5.0
SGI MIPS Pro C++ Compiler, v7.2.1
SGI POSIX 1003.1c Thread API
Linux, v2.2 (Red Hat 6.1)
GNU/GCC 2.95.2 C++ compiler
POSIX 1003.1c LinuxThreads v0.8 API
DEC OSF/1 (Digital Unix), v4.0 f
DEC CXX C++ Compiler, v6.1
DEC POSIX 1003.1c Thread API
Sun Microsystems Solaris, v2.6 (SunOS 5.6)
SunPro C++ Compiler, v4.2.0 (with patch 7)
SparcWorks C++Compiler, v.5.0 (with patch 7) Standard Mode
Solaris Thread API
Sun POSIX 1003.1c Thread API
Sun Microsystems Solaris v7
SparcWorks C++Compiler, v.5.0 (with patch 7) Standard Mode and Compatibility Mode
Solaris Thread API
Sun POSIX 1003.1c Thread API
Microsoft Windows NT4.0, Windows 2000, and Windows 95
Microsoft C++ Compiler, v12.00 (MSVC 6.0 with SP3)
Win32 Thread API
Threads.h++ is a cross-platform product. Rogue Wave has attempted to provide the same interface and capabilities across all the platforms supported by this product, without eliminating the functionality required by developers who need access to the full capabilities of the underlying system.
We have come close to meeting that goal. We have provided a programming interface that is the same across all platforms, but whose individual features and behaviors may vary from platform to platform.
The primary purpose of the remainder of this document is to identify and describe the environment-specific features and behavior of this product.
As a cross-platform product, Threads.h++ primarily relies on the C++ preprocessor to automatically configure the product for each supported environment. If you attempt to build or use this product in an unsupported environment, the library will likely fail to compile as it will not know how to configure itself.
©Copyright 2000, Rogue Wave Software, Inc.
Contact Rogue Wave about documentation or support issues.