Nearly all of the I/O classes are parameterized on the type of characters they read and write (The major exception is ios_base at the top of the hierarchy). More...

Collaboration diagram for I/O stream declarations:

typedef std::basic_ios< Char >	STK::ios
	ios for Char

typedef std::basic_streambuf< Char >	STK::streambuf
	streambuf for Char

typedef std::basic_istream< Char >	STK::istream
	istream for Char

typedef std::basic_ostream< Char >	STK::ostream
	ostream for Char

typedef std::basic_iostream< Char >	STK::iostream
	iostream for Char

typedef std::basic_stringbuf< Char >	STK::stringbuf
	stringbuf for Char

typedef std::basic_istringstream< Char >	STK::istringstream
	istringstream for Char

typedef std::basic_ostringstream< Char >	STK::ostringstream
	ostringstream (ostringstream) for Char

typedef std::basic_stringstream< Char >	STK::stringstream
	stringstream for Char

typedef std::basic_filebuf< Char >	STK::filebuf
	filebuf for Char

typedef std::basic_ifstream< Char >	STK::ifstream
	ifstream for Char

typedef std::basic_ofstream< Char >	STK::ofstream
	ofstream for Char

typedef std::basic_fstream< Char >	STK::fstream

Detailed Description

Nearly all of the I/O classes are parameterized on the type of characters they read and write (The major exception is ios_base at the top of the hierarchy).

For ease of use, all of the basic_* I/O-related classes are given typedef names in the namespace STK. For example:

typedef basic_ifstream<Char> ifstream;

These declarations in the STK namespace would be very useful if you modify the built-in type representation of Char (say wchar_t).