Rogue Wave's implementation of the standard iostreams has several extensions that we describe briefly in the sections below.
The traditional iostreams allowed a file stream to connect to a file using a file descriptor. File descriptors are used by functions like open(), close(), read(), and write() that are part of most C libraries, especially on UNIX-based platforms. However, the ISO/ANSI standard for the programming language C and its library does not include these functions, nor does it mention file descriptors. In this sense, the use of file descriptors introduces platform and operating system dependencies into your program. This is exactly why the standard iostreams does not use file descriptors.
Now you might already have programs that use the file descriptor features of the traditional iostreams. And you may need to access system-specific files like pipes, which are accessible only through file descriptors. To address these concerns, Rogue Wave's implementation offers additional constructors and member functions in the file stream and file buffer classes that enable you to work with file descriptors.
The main additions are:
Constructors that take a file descriptor rather than a file name
An additional third parameter that allows specification of file access rights. This parameter, available on several constructors and the open() member functions, is not available with the standard interface. The parameter has a default, so that you usually need not worry about file protection.
See Chapter 23 on multithreading. Note that all multithreading features are an extension of the standard and are therefore not portable to other implementations of the library.
OEM Edition, ©Copyright 1999, Rogue Wave Software, Inc.
Contact Rogue Wave about documentation or support issues.