Sans Pareil Technologies, Inc.

Key To Your Business

Lesson 10 - File IO

C++ provides the following classes to perform output and input of characters to/from files:
  • std::ofstream: Stream class to write to files
  • std::ifstream: Stream class to read from files
  • std::fstream: Stream class to both read and write to/from files.

These classes are derived directly or indirectly from the classes std::istream and std::ostream. std::cin is an object of class std::istream and std::cout is an object of class std::ostream. File streams are used the same way as std::cin and std::cout, with the only difference that these streams are associated with physical files.

#include <iostream>
#include <fstream>

int main()
  std::ofstream myfile;"example.txt");
  myfile << "Writing this to a file.\n";
  return 0;

This code creates a file called example.txt and inserts a sentence into it in the same way we are used to do with std::cout, but using the file stream myfile instead.

Open a file

The first operation generally performed on an object of one of these classes is to associate it to a real file. This procedure is known as open a file. An open file is represented within a program by a stream (i.e., an object of one of these classes; in the previous example, this was myfile) and any input or output operation performed on this stream object will be applied to the physical file associated to it.

In order to open a file with a stream object we use its member function open:

open (filename, mode);

Where filename is a string representing the name of the file to be opened, and mode is an optional parameter with a combination of the following flags:

std::ios::inOpen for input operations.
std::ios::outOpen for output operations.
std::ios::binaryOpen in binary mode.
std::ios::ateSet the initial position at the end of the file.
If this flag is not set, the initial position is the beginning of the file.
std::ios::appAll output operations are performed at the end of the file, appending the content to the current content of the file.
std::ios::truncIf the file is opened for output operations and it already existed, its previous content is deleted and replaced by the new one.

All these flags can be combined using the bitwise operator OR (|). For example, if we want to open the file example.bin in binary mode to add data we could do it by the following call to member function open:

std::ofstream myfile;"example.bin", std::ios::out | std::ios::app | std::ios::binary);

Each of the open member functions of classes std::ofstream, std::ifstream and std::fstream has a default mode that is used if the file is opened without a second argument:


default mode parameter


std::fstreamstd::ios::in | std::ios::out

For std::ifstream and std::ofstream classes, std::ios::in and std::ios::out are automatically and respectively assumed, even if a mode that does not include them is passed as second argument to the open member function (the flags are combined).

For std::fstream, the default value is only applied if the function is called without specifying any value for the mode parameter. If the function is called with any value in that parameter the default mode is overridden, not combined.

File streams opened in binary mode perform input and output operations independently of any format considerations. Non-binary files are known as text files, and some translations may occur due to formatting of some special characters (like newline and carriage return characters).

Since the first task that is performed on a file stream is generally to open a file, these three classes include a constructor that automatically calls the open member function and has the exact same parameters as this member. Therefore, we could also have declared the previous myfile object and conduct the same opening operation in our previous example by writing:

std::ofstream myfile ("example.bin", std::ios::out | std::ios::app | std::ios::binary);

Combining object construction and stream opening in a single statement. Both forms to open a file are valid and equivalent.

To check if a file stream was successful opening a file, you can do it by calling to member is_open. This member function returns a bool value of true in the case that indeed the stream object is associated with an open file, or false otherwise:

if (myfile.is_open()) { /* ok, proceed with output */ }

Closing a file

When we are finished with our input and output operations on a file we shall close it so that the operating system is notified and its resources become available again. For that, we call the stream's member function close. This member function flushes the associated buffers and closes the file:


Once this member function is called, the stream object can be re-used to open another file, and the file is available again to be opened by other processes.

In case that an object is destroyed while still associated with an open file, the destructor automatically calls the member function close.

Text files

Text file streams are those where the std::ios::binary flag is not included in their opening mode. These files are designed to store text and thus all values that are input or output from/to them can suffer some formatting transformations, which do not necessarily correspond to their literal binary value.

Writing operations on text files are performed in the same way we operated with std::cout

#include <iostream>
#include <fstream>

int main()
  std::ofstream myfile{“example.txt”};
  if (myfile.is_open())
    myfile << "This is a line.\n";
    myfile << "This is another line.\n";
  else std::cout << "Unable to open file" << std::endl;
  return 0;

#include <iostream>
#include <fstream>
#include <string>

int main()
  std::string line;
  std::ifstream myfile{“example.txt”};
  if (myfile.is_open())
    while ( std::getline(myfile,line) )
      std::cout << line << std::endl;
  else std::cout << "Unable to open file" << std::endl;
  return 0;

This last example reads a text file and prints out its content on the screen. We have created a while loop that reads the file line by line, using std::getline function. The value returned by std::getline is a reference to the stream object itself, which when evaluated as a boolean expression (as in this while-loop) is true if the stream is ready for more operations, and false if either the end of the file has been reached or if some other error occurred.

Checking state flags

The following member functions exist to check for specific states of a stream (all of them return a bool value):
  • bad() - Returns true if a reading or writing operation fails. For example, in the case that we try to write to a file that is not open for writing or if the device where we try to write has no space left.
  • fail() - Returns true in the same cases as bad(), but also in the case that a format error happens, like when an alphabetical character is extracted when we are trying to read an integer number.
  • eof() - Returns true if a file open for reading has reached the end.
  • good() - It is the most generic state flag: it returns false in the same cases in which calling any of the previous functions would return true. Note that good() and bad() are not exact opposites (good() checks more state flags at once).

The member function clear() can be used to reset the state flags.

Stream positioning

All I/O stream objects keep internally at least one internal position:
  • std::ifstream, like std::istream, keeps an internal get position with the location of the element to be read in the next input operation.
  • std::ofstream, like std::ostream, keeps an internal put position with the location where the next element has to be written.
  • Finally, std::fstream, keeps both, the get and the put position, like std::iostream.

These internal stream positions point to the locations within the stream where the next reading or writing operation is performed. These positions can be observed and modified using the following member functions:

tellg() and tellp()

These two member functions with no parameters return a value of the member type std::streampos, which is a type representing the current get position (in the case of tellg()) or the put position (in the case of tellp()).

seekg() and seekp()

These functions allow to change the location of the get and put positions. Both functions are overloaded with two different prototypes. The first form is:

seekg( position );
seekp( position );

Using this prototype, the stream pointer is changed to the absolute position (counting from the beginning of the file). The type for this parameter is std::streampos, which is the same type as returned by functions tellg() and tellp().

The other form for these functions are:

seekg( offset, direction );
seekp( offset, direction );

Using this prototype, the get or put position is set to an offset value relative to some specific point determined by the parameter direction. offset is of type std::streamoff. And direction is of type std::seekdir, which is an enumerated type that determines the point from where offset is counted from, and that can take any of the following values:

std::ios::begoffset counted from the beginning of the stream
std::ios::curoffset counted from the current position
std::ios::endoffset counted from the end of the stream

#include <iostream>
#include <fstream>

int main()
  std::streampos begin,end;
  std::ifstream myfile{“example.bin", ios::binary};
  begin = myfile.tellg();
  myfile.seekg(0, ios::end);
  end = myfile.tellg();
  std::cout << "size is: " << (end-begin) << " bytes." << std::endl;
  return 0;

std::streampos is a specific type used for buffer and file positioning and is the type returned by tellg(). Values of this type can safely be subtracted from other values of the same type, and can also be converted to an integer type large enough to contain the size of the file.

These stream positioning functions use two particular types: std::streampos and std::streamoff. These types are also defined as member types of the stream class:


Member type


std::ios::pos_typeDefined as fpos<mbstate_t>.
It can be converted to/from streamoff and can be added or subtracted values of these types.
std::streamoffstd::ios::off_typeIt is an alias of one of the fundamental integral types (such as int or long long).

Each of the member types above is an alias of its non-member equivalent (they are the exact same type). It does not matter which one is used. The member types are more generic, because they are the same on all stream objects (even on streams using exotic types of characters), but the non-member types are widely used in existing code for historical reasons.

Binary files

For binary files, reading and writing data with the extraction and insertion operators (<< and >>) and functions like getline() is not efficient, since we do not need to format any data and data is likely not formatted in lines.

File streams include two member functions specifically designed to read and write binary data sequentially: write and read. The first one (write) is a member function of std::ostream (inherited by std::ofstream). And read is a member function of std::istream (inherited by std::ifstream). Objects of class std::fstream have both. Their prototypes are:

write ( memory_block, size );
read ( memory_block, size );

Where memory_block is of type char* (pointer to char), and represents the address of an array of bytes where the read data elements are stored or from where the data elements to be written are taken. The size parameter is an integer value that specifies the number of characters to be read or written from/to the memory block.

#include <iostream>
#include <fstream>

int main()
  std::streampos size;
  char* memblock;

  std::ifstream file{“example.bin", std::ios::in|std::ios::binary|std::ios::ate};
  if (file.is_open())
    size = file.tellg();
    memblock = new char [size];
    file.seekg(0, std::ios::beg);, size);

    std::cout << "the entire file content is in memory" << std::endl;

    delete[] memblock;
  else std::cout << "Unable to open file" << std::endl;
  return 0;

First, the file is open with the std::ios::ate flag, which means that the get pointer will be positioned at the end of the file. This way, when we call member tellg(), we will directly obtain the size of the file.

Once we have obtained the size of the file, we request the allocation of a memory block large enough to hold the entire file:

memblock = new char[size];

Right after that, we proceed to set the get position at the beginning of the file (remember that we opened the file with this pointer at the end), then we read the entire file, and finally close it:

file.seekg(0, std::ios::beg);, size);

At this point we could operate with the data obtained from the file.

Buffers and Synchronisation

When we operate with file streams, these are associated to an internal buffer object of type std::streambuf. This buffer object may represent a memory block that acts as an intermediary between the stream and the physical file. For example, with an std::ofstream, each time the member function put (which writes a single character) is called, the character may be inserted in this intermediate buffer instead of being written directly to the physical file with which the stream is associated.

The operating system may also define other layers of buffering for reading and writing to files.

When the buffer is flushed, all the data contained in it is written to the physical medium (if it is an output stream). This process is called synchronisation and takes place under any of the following circumstances:
  • When the file is closed - before closing a file, all buffers that have not yet been flushed are synchronised and all pending data is written or read to the physical medium.
  • When the buffer is full - Buffers have a certain size. When the buffer is full it is automatically synchronised.
  • Explicitly, with manipulators - When certain manipulators are used on streams, an explicit synchronisation takes place. These manipulators are: flush and endl.
  • Explicitly, with member function sync() - Calling the stream's member function sync() causes an immediate synchronisation. This function returns an int value -1 if the stream has no associated buffer or in case of failure. Otherwise (if the stream buffer was successfully synchronised) it returns 0.


In computer science, in the context of data storage, serialisation is the process of translating data structures or object state into a format that can be stored (for example, in a file or memory buffer, or transmitted across a network connection link) and reconstructed later in the same or another computer environment. When the resulting series of bits is reread according to the serialisation format, it can be used to create a semantically identical clone of the original object. For many complex objects, such as those that make extensive use of pointers/references, this process is not straightforward. Serialisation of object-oriented objects does not include any of their associated methods with which they were previously linked.

This process of serialising an object is also called marshalling an object. The opposite operation, extracting a data structure from a series of bytes, is deserialisation (which is also called unmarshalling).


  • A method of transferring data through the wires (messaging).
  • A method of storing data (in databases, on hard disk drives).
  • A method of remote procedure calls, e.g., as in SOAP.
  • A method for distributing objects, especially in component-based software engineering such as COM, CORBA, etc.
  • A method for detecting changes in time-varying data.

For some of these features to be useful, architecture independence must be maintained. For example, for maximal use of distribution, a computer running on a different hardware architecture should be able to reliably reconstruct a serialised data stream, regardless of endianness. This means that the simpler and faster procedure of directly copying the memory layout of the data structure cannot work reliably for all architectures. Serialising the data structure in an architecture independent format means preventing the problems of byte ordering, memory layout, or simply different ways of representing data structures in different programming languages.


Serialisation breaks the opacity of an abstract data type by potentially exposing private implementation details. Trivial implementations which serialise all data members may violate encapsulation.

To discourage competitors from making compatible products, publishers of proprietary software often keep the details of their programs' serialisation formats a trade secret. Some deliberately obfuscate or even encrypt the serialised data. Yet, interoperability requires that applications be able to understand each other's serialisation formats. Therefore, remote method call architectures such as CORBA define their serialisation formats in detail.