Using C++
Library Headers
C++ Library
Conventions
Iostreams
Conventions
Program
Startup and Termination
All C++ library entities are declared or defined in one or
more standard headers.
To make use of a library entity in a program, write an include directive
that names the relevant standard header. The full set of 51 C++ library headers (along
with the additional 18 Standard
C headers) constitutes a hosted
implementation of the C++ library: <algorithm>, <bitset>, <cassert>, <cctype>, <cerrno>, <cfloat>, <ciso646>, <climits>, <clocale>, <cmath>, <complex>, <csetjmp>, <csignal>, <cstdarg>, <cstddef>, <cstdio>, <cstdlib>, <cstring>, <ctime>, <cwchar>, <cwctype>, <deque>, <exception>, <fstream>, <functional>, <iomanip>, <ios>, <iosfwd>, <iostream>, <istream>, <iterator>, <limits>, <list>, <locale>, <map>, <memory>, <new>, <numeric>, <ostream>, <queue>, <set>, <sstream>, <stack>, <stdexcept>, <streambuf>, <string>, <strstream>, <typeinfo>, <utility>, <valarray>, and <vector>.
A freestanding
implementation of the C++ library provides only a subset
of these headers: <cstddef>,
<cstdlib>
(declaring at least the functions abort, atexit, and exit), <exception>, <limits>, <new>, <typeinfo>, and <cstdarg>.
The C++ library headers have two broader subdivisions, iostreams headers and STL headers.
You include the contents of a standard header by naming it in an include directive, as in:
#include <iostream> /* include I/O facilities */
You can include the standard headers in any order, a standard header more than once, or two or more standard headers that define the same macro or the same type. Do not include a standard header within a declaration. Do not define macros that have the same names as keywords before you include a standard header.
A C++ library header includes any other C++ library headers it needs to define needed types. (Always include explicitly any C++ library headers needed in a translation unit, however, lest you guess wrong about its actual dependencies.) A Standard C header never includes another standard header. A standard header declares or defines only the entities described for it in this document.
Every function in the library is declared in a standard header. Unlike in Standard C, the standard header never provides a masking macro, with the same name as the function, that masks the function declaration and achieves the same effect.
If an implementation
supports namespaces, all names
other than operator delete and operator new
in the C++ library headers are defined in the std namespace, or in a namespace nested
within the std namespace. You refer to the name cin, for example, as std::cin.
Alternatively, you can write the declaration:
using namespace std;
which promotes all library names into the current namespace. Note that macro names are not subject to the rules for nesting namespaces.
Unless specifically indicated otherwise, you may not define
names in the std namespace, or in a namespace nested
within the std namespace.
Despite what the draft C++ Standard says, common practice is
to define in the global namespace all names in the C standard headers, such
as <stdio.h>.
These names are nominally defined in the std
namespace, then promoted for you. In rare cases, you may have to
add the prefix :: or std:: to a library
name to help the translator locate it.
The C++ library obeys much the same conventions as the Standard C library, plus a few more outlined here.
Except for macro names, which obey no scoping rules, all names
in the C++ library are declared in the std
namespace. Including a C++ library header
does not introduce any library names into the current
namespace. You must, for example, refer to the standard input stream cin as std::cin,
even after including the header <iostream>
that declares it. Alternatively, you can incorporate all members
of the std namespace into the current namespace by
writing:
using namespace std;
immediately after all include
directives that name the standard headers. Note that the Standard C headers
behave mostly as if they include no namespace declarations. If
you include, for example, <cstdlib>,
you call std::abort()
to cause abnormal termination, but if you include <stdlib.h>, you
call abort().
An implementation has certain latitude in how it declares types and functions in the C++ library:
extern
"C++" or extern "C"
linkage. Include the appropriate Standard C header
rather than declare a library entity inline.On the other hand, there are some restrictions you can count on:
qsort calls a
comparison function that throws an exception, but they do
not otherwise throw exceptions.The iostreams headers support conversions between text
and encoded forms, and input and output to external files: <fstream>, <iomanip>, <ios>, <iosfwd>, <iostream>, <istream>, <ostream>, <sstream>, <streambuf>, and <strstream>.
The simplest use of iostreams requires only that you include
the header <iostream>. You can then extract
values from cin,
to read the standard input.
The rules for doing so are outlined in the description of the
class basic_istream.
You can also insert values to cout,
to write the standard
output. The rules for doing so are outlined in the
description of the class basic_ostream.
Format control common to both extractors and insertors is managed
by the class basic_ios.
Manipulating this format information in the guise of extracting
and inserting objects is the province of several manipulators.
You can perform the same iostreams operations on files that
you open by name, using the classes declared in <fstream>.
To convert between iostreams and objects of class basic_string,
use the classes declared in <sstream>. And to
do the same with C strings,
use the classes declared in <strstream>.
The remaining headers provide support services, typically of direct interest to only the most advanced users of the iostreams classes.
A C++ program performs the same operations as does a C program program startup and at program termination, plus a few more outlined here.
Before the target environment calls the function main, and after it
stores any constant initial values you specify in all objects
that have static duration, the program executes any remaining
constructors for such static objects. The order of execution is
not specified between translation units, but you can nevertheless
assume that some iostreams objects are
properly initialized for use by these static constructors. These
control text streams:
cin
-- for standard
inputcout
-- for standard
outputcerr
-- for unbuffered standard
error outputclog
-- for buffered standard
error outputYou can also use these objects within the destructors called for static objects, during program termination.
As with C, returning from main
or calling exit
calls all functions registered with atexit in
reverse order of registry. An exception thrown from such a
registered function calls terminate().
See also the Table of Contents.
Copyright © 1992-1996 by P.J. Plauger. All rights reserved.