C++ Library Reference

Chapter 3

The Classic iostream Library

C++, like C, has no built-in input or output statements. Instead, I/O facilities are provided by a library. The Sun WorkShop 6 C++ compiler provides both the classic implementation and the ISO standard implementation of the iostream classes.

• In compatibility mode (-compat[=4]), the classic iostream classes are contained in libC.
• In standard mode (default mode), the classic iostream classes are contained in libiostream. Use libiostream when you have source code that uses the classic iostream classes and you want to compile the source in standard mode. To use the classic iostream facilities in standard mode, include the iostream.h header file and compile using the -library=iostream option.
• The standard iostream classes are available only in standard mode, and are contained in the C++ standard library, libCstd.

This chapter provides an introduction to the classic iostream library and provides examples of its use. This chapter does not provide a complete description of the iostream library. See the iostream library man pages for more details. To access the classic iostream man pages type:

example% man -s 3CC4 name

3.1 Predefined iostreams

There are four predefined iostreams:

• cin, connected to standard input
• cout, connected to standard output
• cerr, connected to standard error
• clog, connected to standard error

The predefined iostreams are fully buffered, except for cerr. See Section 3.3.1 "Output Using iostream" and Section 3.3.2 "Input Using iostream".

3.2 Basic Structure of iostream Interaction

By including the iostream library, a program can use any number of input or output streams. Each stream has some source or sink, which may be one of the following:

• Standard input
• Standard output
• Standard error
• A file
• An array of characters

A stream can be restricted to input or output, or a single stream can allow both input and output. The iostream library implements these streams using two processing layers.

• The lower layer implements sequences, which are simply streams of characters. These sequences are implemented by the streambuf class, or by classes derived from it.
• The upper layer performs formatting operations on sequences. These formatting operations are implemented by the istream and ostream classes, which have as a member an object of a type derived from class streambuf. An additional class, iostream, is for streams on which both input and output can be performed.

Standard input, output, and error are handled by special class objects derived from class istream or ostream.

The ifstream, ofstream, and fstream classes, which are derived from istream, ostream, and iostream respectively, handle input and output with files.

The istrstream, ostrstream, and strstream classes, which are derived from istream, ostream, and iostream respectively, handle input and output to and from arrays of characters.

When you open an input or output stream, you create an object of one of these types, and associate the streambuf member of the stream with a device or file. You generally do this association through the stream constructor, so you don't work with the streambuf directly. The iostream library predefines stream objects for the standard input, standard output, and error output, so you don't have to create your own objects for those streams.

You use operators or iostream member functions to insert data into a stream (output) or extract data from a stream (input), and to control the format of data that you insert or extract.

When you want to insert and extract a new data type--one of your classes--you generally overload the insertion and extraction operators.

3.3 Using the Classic iostream Library

To use routines from the classic iostream library, you must include the header files for the part of the library you need. The header files are described in the following table.

TABLE 3-1   iostream Routine Header Files

Header File	Description
iostream.h	Declares basic features of iostream library.
fstream.h	Declares iostreams and streambufs specialized to files. Includes iostream.h.
strstream.h	Declares iostreams and streambufs specialized to character arrays. Includes iostream.h.
iomanip.h	Declares manipulators: values you insert into or extract from iostreams to have different effects. Includes iostream.h.
stdiostream.h	(obsolete) Declares iostreams and streambufs specialized to use stdio FILEs.Includes iostream.h.
stream.h	(obsolete) Includes iostream.h, fstream.h, iomanip.h, and stdiostream.h. For compatibility with old-style streams from C++ version 1.2.

You usually do not need all of these header files in your program. Include only the ones that contain the declarations you need. In compatibility mode (-compat[=4]), the classic iostream library is part of libC, and is linked automatically by the CC driver. In standard mode (the default), libiostream contains the classic iostream library.

3.3.1 Output Using iostream

Output using iostream usually relies on the overloaded left-shift operator (<<) which, in the context of iostream, is called the insertion operator. To output a value to standard output, you insert the value in the predefined output stream cout. For example, given a value someValue, you send it to standard output with a statement like:

cout << someValue;

The insertion operator is overloaded for all built-in types, and the value represented by someValue is converted to its proper output representation. If, for example, someValue is a float value, the << operator converts the value to the proper sequence of digits with a decimal point. Where it inserts float values on the output stream, << is called the float inserter. In general, given a type X, << is called the X inserter. The format of output and how you can control it is discussed in the ios(3CC4) man page.

The iostream library does not support user-defined types. If you define types that you want to output in your own way, you must define an inserter (that is, overload the << operator) to handle them correctly.

The << operator can be applied repetitively. To insert two values on cout, you can use a statement like the one in the following example:

cout << someValue << anotherValue;

The output from the above example will show no space between the two values. So you may want to write the code this way:

cout << someValue << " " << anotherValue;

The << operator has the precedence of the left shift operator (its built-in meaning). As with other operators, you can always use parentheses to specify the order of action. It is often a good idea to use parentheses to avoid problems of precedence. Of the following four statements, the first two are equivalent, but the last two are not.

cout << a+b; // + has higher precedence than << cout << (a+b); cout << (a&y); // << has precedence higher than & cout << a&y; // probably an error: (cout << a) & y

3.3.1.1 Defining Your Own Insertion Operator

The following example defines a string class:

#include <stdlib.h> #include <iostream.h> class string { private: char* data; size_t size; public: // (functions not relevant here) friend ostream& operator<<(ostream&, const string&); friend istream& operator>>(istream&, string&); };

The insertion and extraction operators must in this case be defined as friends because the data part of the string class is private.

ostream& operator<< (ostream& ostr, const string& output) { return ostr << output.data; }

Here is the definition of operator<< overloaded for use with strings.

cout << string1 << string2;

operator<< takes ostream& (that is, a reference to an ostream) as its first argument and returns the same ostream, making it possible to combine insertions in one statement.

3.3.1.2 Handling Output Errors

Generally, you don't have to check for errors when you overload operator<< because the iostream library is arranged to propagate errors.

When an error occurs, the iostream where it occurred enters an error state. Bits in the iostream's state are set according to the general category of the error. The inserters defined in iostream ignore attempts to insert data into any stream that is in an error state, so such attempts do not change the iostream's state.

In general, the recommended way to handle errors is to periodically check the state of the output stream in some central place. If there is an error, you should handle it in some way. This chapter assumes that you define a function error, which takes a string and aborts the program. error is not a predefined function. See Section 3.3.9 "Handling Input Errors" for an example of an error function. You can examine the state of an iostream with the operator !,which returns a nonzero value if the iostream is in an error state. For example:

if (!cout) error( "output error");

There is another way to test for errors. The ios class defines operator void *(), so it returns a NULL pointer when there is an error. You can use a statement like:

if (cout << x) return ; // return if successful

You can also use the function good, a member of ios:

if ( cout.good() ) return ; // return if successful

The error bits are declared in the enum:

enum io_state { goodbit=0, eofbit=1, failbit=2, badbit=4, hardfail=0x80} ;

For details on the error functions, see the iostream man pages.

3.3.1.3 Flushing

As with most I/O libraries, iostream often accumulates output and sends it on in larger and generally more efficient chunks. If you want to flush the buffer, you simply insert the special value flush. For example:

cout << "This needs to get out immediately." << flush ;

flush is an example of a kind of object known as a manipulator, which is a value that can be inserted into an iostream to have some effect other than causing output of its value. It is really a function that takes an ostream& or istream& argument and returns its argument after performing some actions on it (see Section 3.7 "Manipulators").

3.3.1.4 Binary Output

To obtain output in the raw binary form of a value, use the member function write as shown in the following example. This example shows the output in the raw binary form of x.

cout.write((char*)&x, sizeof(x));

The previous example violates type discipline by converting &x to char*. Doing so is normally harmless, but if the type of x is a class with pointers, virtual member functions, or one that requires nontrivial constructor actions, the value written by the above example cannot be read back in properly.

3.3.2 Input Using iostream

Input using iostream is similar to output. You use the extraction operator >> and you can string together extractions the way you can with insertions. For example:

cin >> a >> b ;

This statement gets two values from standard input. As with other overloaded operators, the extractors used depend on the types of a and b (and two different extractors are used if a and b have different types). The format of input and how you can control it is discussed in some detail in the ios(3CC4) man page. In general, leading whitespace characters (spaces, newlines, tabs, form-feeds, and so on) are ignored.

3.3.3 Defining Your Own Extraction Operators

When you want input for a new type, you overload the extraction operator for it, just as you overload the insertion operator for output.

Class string defines its extraction operator in the following code example:

CODE EXAMPLE 3-1   string Extraction Operator 

istream& operator>> (istream& istr, string& input) { const int maxline = 256; char holder[maxline]; istr.get(holder, maxline, `\n'); input = holder; return istr; }

The get function reads characters from the input stream istr and stores them in holder until maxline-1 characters have been read, or a new line is encountered, or EOF, whichever happens first. The data in holder is then null-terminated. Finally, the characters in holder are copied into the target string.

By convention, an extractor converts characters from its first argument (in this case, istream& istr), stores them in its second argument, which is always a reference, and returns its first argument. The second argument must be a reference because an extractor is meant to store the input value in its second argument.

3.3.4 Using the char* Extractor

This predefined extractor is mentioned here because it can cause problems. Use it like this:

char x[50]; cin >> x;

This extractor skips leading whitespace and extracts characters and copies them to x until it reaches another whitespace character. It then completes the string with a terminating null (0) character. Be careful, because input can overflow the given array.

You must also be sure the pointer points to allocated storage. For example, here is a common error:

char * p; // not initialized cin >> p;

There is no telling where the input data will be stored, and it may cause your program to abort.

3.3.5 Reading Any Single Character

In addition to using the char extractor, you can get a single character with either form of the get member function. For example:

char c; cin.get(c); // leaves c unchanged if input fails int b; b = cin.get(); // sets b to EOF if input fails

---

Note – Unlike the other extractors, the char extractor does not skip leading whitespace.

---

Here is a way to skip only blanks, stopping on a tab, newline, or any other character:

int a; do { a = cin.get(); } while( a == ' ' );

3.3.6 Binary Input

If you need to read binary values (such as those written with the member function write), you can use the read member function. The following example shows how to input the raw binary form of x using the read member function, and is the inverse of the earlier example that uses write.

cin.read((char*)&x, sizeof(x));

3.3.7 Peeking at Input

You can use the peek member function to look at the next character in the stream without extracting it. For example:

if (cin.peek() != c) return 0;

3.3.8 Extracting Whitespace

By default, the iostream extractors skip leading whitespace. You can turn off the skip flag to prevent this from happening. The following example turns off whitespace skipping from cin, then turns it back on:

cin.unsetf(ios::skipws); // turn off whitespace skipping . . . cin.setf(ios::skipws); // turn it on again

You can use the iostream manipulator ws to remove leading whitespace from the iostream, whether or not skipping is enabled. The following example shows how to remove the leading whitespace from iostream istr:

istr >> ws;

3.3.9 Handling Input Errors

By convention, an extractor whose first argument has a nonzero error state should not extract anything from the input stream and should not clear any error bits. An extractor that fails should set at least one error bit.

As with output errors, you should check the error state periodically and take some action, such as aborting, when you find a nonzero state. The ! operator tests the error state of an iostream. For example, the following code produces an input error if you type alphabetic characters for input:

#include <unistd.h> #include <iostream.h> void error (const char* message) { cerr << message << "\n" ; exit(1); } int main() { cout << "Enter some characters: "; int bad; cin >> bad; if (!cin) error("aborted due to input error"); cout << "If you see this, not an error." << "\n"; return 0; }

Class ios has member functions that you can use for error handling. See the man pages for details.

3.3.10 Using iostreams with stdio

You can use stdio with C++ programs, but problems can occur when you mix iostreams and stdio in the same standard stream within a program. For example, if you write to both stdout and cout, independent buffering occurs and produces unexpected results. The problem is worse if you input from both stdin and cin, since independent buffering may turn the input into trash.

To eliminate this problem with standard input, standard output and standard error, use the following instruction before performing any input or output. It connects all the predefined iostreams with the corresponding predefined stdio FILEs.

ios::sync_with_stdio();

Such a connection is not the default because there is a significant performance penalty when the predefined streams are made unbuffered as part of the connection. You can use both stdio and iostreams in the same program applied to different files. That is, you can write to stdout using stdio routines and write to other files attached to iostreams. You can open stdio FILEs for input and also read from cin so long as you don't also try to read from stdin.

3.4 Creating iostreams

To read or write a stream other than the predefined iostreams, you need to create your own iostream. In general, that means creating objects of types defined in the iostream library. This section discusses the various types available.

3.4.1 Dealing with Files Using Class fstream

Dealing with files is similar to dealing with standard input and standard output; classes ifstream, ofstream, and fstream are derived from classes istream, ostream, and iostream, respectively. As derived classes, they inherit the insertion and extraction operations (along with the other member functions) and also have members and constructors for use with files.

Include the file fstream.h to use any of the fstreams. Use an ifstream when you only want to perform input, an ofstream for output only, and an fstream for a stream on which you want to perform both input and output. Use the name of the file as the constructor argument.

For example, copy the file thisFile to the file thatFile as in the following example:

ifstream fromFile("thisFile"); if (!fromFile) error("unable to open 'thisFile' for input"); ofstream toFile ("thatFile"); if ( !toFile ) error("unable to open 'thatFile' for output"); char c ; while (toFile && fromFile.get(c)) toFile.put(c);

This code:

• Creates an ifstream object called fromFile with a default mode of ios::in and connects it to thisFile. It opens thisFile.
• Checks the error state of the new ifstream object and, if it is in a failed state, calls the error function, which must be defined elsewhere in the program.
• Creates an ofstream object called toFile with a default mode of ios::out and connects it to thatFile.
• Checks the error state of toFile as above.
• Creates a char variable to hold the data while it is passed.
• Copies the contents of fromFile to toFile one character at a time.

  ---

  Note – It is, of course, undesirable to copy a file this way, one character at a time. This code is provided just as an example of using fstreams. You should instead insert the streambuf associated with the input stream into the output stream. See Section 3.10 "Streambufs", and the man page sbufpub(3CC4).

  ---

3.4.1.1 Open Mode

The mode is constructed by or-ing bits from the enumerated type open_mode, which is a public type of class ios and has the definition:

enum open_mode {binary=0, in=1, out=2, ate=4, app=8, trunc=0x10, nocreate=0x20, noreplace=0x40};

---

Note – The binary flag is not needed on Unix, but is provided for compatibility with systems that do need it. Portable code should use the binary flag when opening binary files.

---

You can open a file for both input and output. For example, the following code opens file someName for both input and output, attaching it to the fstream variable inoutFile.

fstream inoutFile("someName", ios::in|ios::out);

3.4.1.2 Declaring an fstream Without Specifying a File

You can declare an fstream without specifying a file and open the file later. For example, the following creates the ofstream toFile for writing.

ofstream toFile; toFile.open(argv[1], ios::out);

3.4.1.3 Opening and Closing Files

You can close the fstream and then open it with another file. For example, to process a list of files provided on the command line:

ifstream infile; for (char** f = &argv[1]; *f; ++f) { infile.open(*f, ios::in); ...; infile.close(); }

3.4.1.4 Opening a File Using a File Descriptor

If you know a file descriptor, such as the integer 1 for standard output, you can open it like this:

ofstream outfile; outfile.attach(1);

When you open a file by providing its name to one of the fstream constructors or by using the open function, the file is automatically closed when the fstream is destroyed (by a delete or when it goes out of scope). When you attach a file to an fstream, it is not automatically closed.

3.4.1.5 Repositioning within a File

You can alter the reading and writing position in a file. Several tools are supplied for this purpose.

• streampos is a type that can record a position in an iostream.
• tellg (tellp) is an istream (ostream) member function that reports the file position. Since istream and ostream are the parent classes of fstream, tellg and tellp can also be invoked as a member function of the fstream class.
• seekg (seekp) is an istream (ostream) member function that finds a given position.
• The seek_dir enum specifies relative positions for use with seek.

  enum seek_dir { beg=0, cur=1, end=2 }

For example, given an fstream aFile:

streampos original = aFile.tellp(); //save current position aFile.seekp(0, ios::end); //reposition to end of file aFile << x; //write a value to file aFile.seekp(original); //return to original position

seekg (seekp) can take one or two parameters. When it has two parameters, the first is a position relative to the position indicated by the seek_dir value given as the second parameter. For example:

aFile.seekp(-10, ios::end);

moves to 10 bytes from the end while

aFile.seekp(10, ios::cur);

moves to 10 bytes forward from the current position.

---

Note – Arbitrary seeks on text streams are not portable, but you can always return to a previously saved streampos value.

---

3.5 Assignment of iostreams

iostreams does not allow assignment of one stream to another.

The problem with copying a stream object is that there are then two versions of the state information, such as a pointer to the current write position within an output file, which can be changed independently. As a result, problems could occur.

3.6 Format Control

Format control is discussed in detail in the in the man page ios(3CC4).

3.7 Manipulators

Manipulators are values that you can insert into or extract from iostreams to have special effects.

Parameterized manipulators are manipulators that take one or more parameters.

Because manipulators are ordinary identifiers, and therefore use up possible names, iostream doesn't define them for every possible function. A number of manipulators are discussed with member functions in other parts of this chapter.

There are 13 predefined manipulators, as described in TABLE 3-2. When using that table, assume the following:

• i has type long.
• n has type int.
• c has type char.
• istr is an input stream.
• ostr is an output stream.

  TABLE 3-2   iostream Predefined Manipulators 

  	Predefined Manipulator	Description
  1	ostr << dec, istr >> dec	Makes the integer conversion base 10.
  2	ostr << endl	Inserts a newline character ('\n') and invokes ostream::flush().
  3	ostr << ends	Inserts a null (0) character. Useful when dealing with strstreams.
  4	ostr << flush	Invokes ostream::flush().
  5	ostr << hex, istr >> hex	Makes the integer conversion base 16.
  6	ostr << oct, istr >> oct	Make the integer conversion base 8.
  7	istr >> ws	Extracts whitespace characters (skips whitespace) until a non-whitespace character is found (which is left in istr).
  8	ostr << setbase(n), istr >> setbase(n)	Sets the conversion base to n (0, 8, 10, 16 only).
  9	ostr << setw(n), istr >> setw(n)	Invokes ios::width(n). Sets the field width to n.
  10	ostr << resetiosflags(i), istr >> resetiosflags(i)	Clears the flags bitvector according to the bits set in i.
  11	ostr << setiosflags(i), istr >> setiosflags(i)	Sets the flags bitvector according to the bits set in i.
  12	ostr << setfill(c), istr >> setfill(c)	Sets the fill character (for padding a field) to c.
  13	ostr << setprecision(n), istr >> setprecision(n)	Sets the floating-point precision to n digits.

  
  

To use predefined manipulators, you must include the file iomanip.h in your program.

You can define your own manipulators. There are two basic types of manipulator:

• Plain manipulator--Takes an istream&, ostream&, or ios& argument, operates on the stream, and then returns its argument.
• Parameterized manipulator--Takes an istream&, ostream&, or ios& argument, one additional argument (the parameter), operates on the stream, and then returns its stream argument.

3.7.1 Using Plain Manipulators

A plain manipulator is a function that:

• Takes a reference to a stream
• Operates on it in some way
• Returns its argument

The shift operators taking (a pointer to) such a function are predefined for iostreams, so the function can be put in a sequence of input or output operators. The shift operator calls the function rather than trying to read or write a value. An example of a tab manipulator that inserts a tab in an ostream is:

ostream& tab(ostream& os) { return os << '\t' ; } ... cout << x << tab << y ;

This is an elaborate way to achieve the following:

const char tab = '\t'; ... cout << x << tab << y;

Here is another example, which cannot be accomplished with a simple constant. Suppose you want to turn whitespace skipping on and off for an input stream. You can use separate calls to ios::setf and ios::unsetf to turn the skipws flag on and off, or you could define two manipulators:

#include <iostream.h> #include <iomanip.h> istream& skipon(istream &is) {        is.setf(ios::skipws, ios::skipws);        return is; } istream& skipoff(istream& is) {        is.unsetf(ios::skipws);        return is; } ... int main () {       int x,y;       cin >> skipon >> x >> skipoff >> y;       return 1; }

3.7.2 Parameterized Manipulators

One of the parameterized manipulators that is included in iomanip.h is setfill. setfill sets the character that is used to fill out field widths. It is implemented as shown in the following example:

//file setfill.cc #include<iostream.h> #include<iomanip.h> //the private manipulator static ios& sfill(ios& i, int f) { i.fill(f); return i; } //the public applicator smanip_int setfill(int f) { return smanip_int(sfill, f); }

A parameterized manipulator is implemented in two parts:

• The manipulator. It takes an extra parameter. In the previous code example, it takes an extra int parameter. You cannot place this manipulator function in a sequence of input or output operations, since there is no shift operator defined for it. Instead, you must use an auxiliary function, the applicator.
• The applicator. It calls the manipulator. The applicator is a global function, and you make a prototype for it available in a header file. Usually the manipulator is a static function in the file containing the source code for the applicator. The manipulator is called only by the applicator, and if you make it static, you keep its name out of the global address space.

Several classes are defined in the header file iomanip.h. Each class holds the address of a manipulator function and the value of one parameter. The iomanip classes are described in the man page manip(3CC4). The previous example uses the smanip_int class, which works with an ios. Because it works with an ios, it also works with an istream and an ostream. The previous example also uses a second parameter of type int.

The applicator creates and returns a class object. In the previous code example the class object is an smanip_int, and it contains the manipulator and the int argument to the applicator. The iomanip.h header file defines the shift operators for this class. When the applicator function setfill appears in a sequence of input or output operations, the applicator function is called, and it returns a class. The shift operator acts on the class to call the manipulator function with its parameter value, which is stored in the class.

In the following example, the manipulator print_hex:

• Puts the output stream into the hex mode.
• Inserts a long value into the stream.
• Restores the conversion mode of the stream.

The class omanip_long is used because this code example is for output only, and it operates on a long rather than an int:

#include <iostream.h> #include <iomanip.h> static ostream& xfield(ostream& os, long v) { long save = os.setf(ios::hex, ios::basefield); os << v; os.setf(save, ios::basefield); return os; } omanip_long print_hex(long v) { return omanip_long(xfield, v); }

3.8 Strstreams: iostreams for Arrays

See the strstream(3CC4) man page.

3.9 Stdiobufs: iostreams for stdio Files

See the stdiobuf(3CC4) man page.

3.10 Streambufs

iostreams are the formatting part of a two-part (input or output) system. The other part of the system is made up of streambufs, which deal in input or output of unformatted streams of characters.

You usually use streambufs through iostreams, so you don't have to worry about the details of streambufs. You can use streambufs directly if you choose to, for example, if you need to improve efficiency or to get around the error handling or formatting built into iostreams.

3.10.1 Working with Streambufs

A streambuf consists of a stream or sequence of characters and one or two pointers into that sequence. Each pointer points between two characters. (Pointers cannot actually point between characters, but it is helpful to think of them that way.) There are two kinds of streambuf pointers:

• A put pointer, which points just before the position where the next character will be stored
• A get pointer, which points just before the next character to be fetched

A streambuf can have one or both of these pointers.

3.10.1.1 Position of Pointers

The positions of the pointers and the contents of the sequences can be manipulated in various ways. Whether or not both pointers move when manipulated depends on the kind of streambuf used. Generally, with queue-like streambufs, the get and put pointers move independently; with file-like streambufs the get and put pointers always move together. A strstream is an example of a queue-like stream; an fstream is an example of a file-like stream.

3.10.2 Using Streambufs

You never create an actual streambuf object, but only objects of classes derived from class streambuf. Examples are filebuf and strstreambuf, which are described in man pages filebuf(3CC4) and ssbuf(3), respectively. Advanced users may want to derive their own classes from streambuf to provide an interface to a special device or to provide other than basic buffering. Man pages sbufpub(3CC4) and sbufprot(3CC4) discuss how to do this.

Apart from creating your own special kind of streambuf, you may want to access the streambuf associated with an iostream to access the public member functions, as described in the man pages referenced above. In addition, each iostream has a defined inserter and extractor which takes a streambuf pointer. When a streambuf is inserted or extracted, the entire stream is copied.

Here is another way to do the file copy discussed earlier, with the error checking omitted for clarity:

ifstream fromFile("thisFile"); ofstream toFile ("thatFile"); toFile << fromFile.rdbuf();

We open the input and output files as before. Every iostream class has a member function rdbuf that returns a pointer to the streambuf object associated with it. In the case of an fstream, the streambuf object is type filebuf. The entire file associated with fromFile is copied (inserted into) the file associated with toFile. The last line could also be written like this:

fromFile >> toFile.rdbuf();

The source file is then extracted into the destination. The two methods are entirely equivalent.

3.11 iostream Man Pages

A number of C++ man pages give details of the iostream library. The following table gives an overview of what is in each man page.

To access a classic iostream library man page, type:

example% man -s 3CC4 name

    

TABLE 3-3   iostream Man Pages Overview 

Man Page	Overview
filebuf	Details the public interface for the class filebuf, which is derived from streambuf and is specialized for use with files. See the sbufpub(3CC4) and sbufprot(3CC4) man pages for details of features inherited from class streambuf. Use the filebuf class through class fstream.
fstream	Details specialized member functions of classes ifstream, ofstream, and fstream, which are specialized versions of istream, ostream, and iostream for use with files.
ios	Details parts of class ios, which functions as a base class for iostreams. It contains state data common to all streams.
ios.intro	Gives an introduction to and overview of iostreams.
istream	Details the following: Member functions for class istream, which supports interpretation of characters fetched from a streambuf Input formatting Positioning functions described as part of class ostream. Some related functions Related manipulators
manip	Describes the input and output manipulators defined in the iostream library.
ostream	Details the following: Member functions for class ostream, which supports interpretation of characters written to a streambuf Output formatting Positioning functions described as part of class ostream Some related functions Related manipulators
sbufprot	Describes the interface needed by programmers who are coding a class derived from class streambuf. Also refer to the sbufpub(3CC4) man page because some public functions are not discussed in the sbufprot(3CC4) man page.
sbufpub	Details the public interface of class streambuf, in particular, the public member functions of streambuf. This man page contains the information needed to manipulate a streambuf-type object directly, or to find out about functions that classes derived from streambuf inherit from it. If you want to derive a class from streambuf, also see the sbufprot(3CC4) man page.
ssbuf	Details the specialized public interface of class strstreambuf, which is derived from streambuf and specialized for dealing with arrays of characters. See the sbufpub(3CC4) man page for details of features inherited from class streambuf.
stdiobuf	Contains a minimal description of class stdiobuf, which is derived from streambuf and specialized for dealing with stdio FILEs. See the sbufpub(3CC4) man page for details of features inherited from class streambuf.
strstream	Details the specialized member functions of strstreams, which are implemented by a set of classes derived from the iostream classes and specialized for dealing with arrays of characters.

3.12 iostream Terminology

The iostream library descriptions often use terms similar to terms from general programming, but with specialized meanings. The following table defines these terms as they are used in discussing the iostream library.

TABLE 3-4   iostream Terminology 

iostream Term	Definition
Buffer	A word with two meanings, one specific to the iostream package and one more generally applied to input and output. When referring specifically to the iostream library, a buffer is an object of the type defined by the class streambuf. A buffer, generally, is a block of memory used to make efficient transfer of characters for input of output. With buffered I/O, the actual transfer of characters is delayed until the buffer is full or forcibly flushed. An unbuffered buffer refers to a streambuf where there is no buffer in the general sense defined above. This chapter avoids use of the term buffer to refer to streambufs. However, the man pages and other C++ documentation do use the term buffer to mean streambufs.
Extraction	The process of taking input from an iostream.
Fstream	An input or output stream specialized for use with files. Refers specifically to a class derived from class iostream when printed in courier font.
Insertion	The process of sending output into an iostream.
iostream	Generally, an input or output stream.
iostream library	The library implemented by the include files iostream.h, fstream.h, strstream.h, iomanip.h, and stdiostream.h. Because iostream is an object-oriented library, you should extend it. So, some of what you can do with the iostream library is not implemented.
Stream	An iostream, fstream, strstream, or user-defined stream in general.
Streambuf	A buffer that contains a sequence of characters with a put or get pointer, or both. When printed in courier font, it means the particular class. Otherwise, it refers generally to any object of class streambuf or a class derived from streambuf. Any stream object contains an object, or a pointer to an object, of a type derived from streambuf.
Strstream	An iostream specialized for use with character arrays. It refers to the specific class when printed in courier font.