Home/ Questions/Q 3362688
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T03:18:16+00:00

If I do something like the following: ifstream file; file.open(somefile, ios::binary); unsigned int data;

  • 0

If I do something like the following:

ifstream file;
file.open("somefile", ios::binary);

unsigned int data;

file >> data;

My stream will always set the failbit and the data will remain uninitialized. However, if I read a char or unsigned char instead, the stream is fine. perror() is telling me “result too large”.

The only thing I saw on Google was a suggestion saying that operator>> shouldn’t be used for binary data (prefer read()), but I find the operator to be cleaner and easier to use — and it doesn’t require casting everything.

Can someone explain this issue?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The iostream extraction operator (>>) attempts to interpret numerical strings separated by whitespace, not binary data. There are many different ways to encode an unsigned integer in binary form (e.g. a 32-bit 2’s complement representation in little-endian byte order). That’s why you must use the read/write functions to operate on such binary buffers.

    However, nothing prevents you from implementing your own class for serializing binary data in whatever form you wish using the insertion and extraction operators. Such a class would likely use the read function of an ifstream object internally. Alternatively, the boost serialization library may already hold exactly what you want.

    • 0