Jump to content

  • Log In with Google      Sign In   
  • Create Account


Tips for Cross-Platform I/O in C/C++

By John Bolton | Published May 03 2005 05:06 PM in Game Programming

byte unsigned order signed char data compiler read certain
If you find this article contains errors or problems rendering it unreadable (missing images or files, mangled code, improper text formatting, etc) please contact the editor so corrections can be made. Thank you for helping us improve this resource

If you are writing cross-platform C/C++ code that reads or writes data from/to a file or over the network, then you have to be aware of issues related to language, compiler, and platform
differences. The major issues are data alignment, padding, sizes of types, byte order, and whether char is signed or unsigned by default.


Certain data has to be aligned on certain boundaries on certain machines. If the data is not aligned properly, the results can vary from poor performance to a crash. When you read data from an I/O
source into memory, make sure it is aligned correctly.


"Padding" is space added between elements in aggregated data, usually to ensure that they are properly aligned. The amount of padding may differ between compilers and platforms. Do not assume that
the size of a struct and the location of its members are the same for all compilers and platforms. Do not read or write an entire struct at once
because the program that writes the data might pad it differently than the the program that reads it. This applies to fields, too.

Sizes of Types

The sizes of variable types can differ depending on the platform and compiler. In C/C++, the size of an intrinsic type is completely up to the compiler (within certain constraints). Do not read or
write types whose sizes are not explicitly specified. In other words, do not read or write bools, enums, longs,
ints, shorts, floats, or doubles.

Use these... ...instead of these
int8, uint8char, signed char, unsigned char, enum, "code">bool
int16, uint16short, signed short, unsigned short, enum
int32, uint32int, signed int, unsigned int, long, "code">signed long, unsigned long, enum
int64, uint64long, signed long, unsigned long
int128, uint128long long, signed long long, unsigned long long

Byte order

The byte order of a value is the order that the bytes are stored in memory. Different processors store multi-byte numbers in memory in different orders. Little-endian processors store bytes
in the order of least significant byte to most significant byte (in other words, backwards from the way numbers are written). Big-endian processors store bytes in the order of most significant
byte to least significant byte (the same way numbers are written). If the byte order of a value does not match the byte order of the processor that is reading or writing it, then it must be
converted. Also, as a way to standardize the order of bytes transmitted over a network, there is a network byte order.

char - signed or unsigned?

A little-known fact is that char can be signed or unsigned by default -- it is up to the compiler. The result is that when you convert from char
to another type (such as int), the result can differ depending on the compiler. For example:

char   x;

int    y;

read( fd, &x, 1 );   // read a byte with the value 0xff

y = x;               // y is 255 or -1, depending on the compiler

Do not read a value into a generic char. Always specify signed or unsigned.


Note: Please offer only positive, constructive comments - we are looking to promote a positive atmosphere where collaboration is valued above all else.