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?
The best way to read a binary number is to start with the right-most digit and work your way left. The power of that first location is zero, meaning the value for that digit, if it's not a zero, is two to the power of zero, or one. In this case, since the digit is a zero, the value for this place would be zero.
Use the fread Function to Read Binary File in C fread is part of the C standard library input/output facilities, and it can be utilized to read binary data from regular files.
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.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With