736
edits
Difference between revisions of "Coding Conventions"
m
→Endianess issues: MACOSX
(Mention that portability is one of our design goals.) |
m (→Endianess issues: MACOSX) |
||
| Line 18: | Line 18: | ||
ScummVM engine authors have to keep endianess issues in mind for two reasons: | ScummVM engine authors have to keep endianess issues in mind for two reasons: | ||
* ScummVM runs on both little endian (Windows, Intel Mac OS X, Intel Linux, ...) and big end hosts (PowerPC Mac OS X, ...). So when writing data (think savegames) to files and reading it back again, you need to compensate for this. This is easily done by using the READ_ and WRITE_ macros from common/endian.h (like READ_LE_UINT32 or WRITE_BE_UINT16.) resp. the corresponding Stream class methods (like readUint32LE or writeUint16BE) | * ScummVM runs on both little endian (Windows, Intel Mac OS X, Intel Linux, ...) and big end hosts (PowerPC Mac OS X, ...). So when writing data (think savegames) to files and reading it back again, you need to compensate for this. This is easily done by using the READ_ and WRITE_ macros from common/endian.h (like READ_LE_UINT32 or WRITE_BE_UINT16.) resp. the corresponding Stream class methods (like readUint32LE or writeUint16BE) | ||
* Furthermore, some games existed in multiple versions, e.g. one for Windows and one for | * Furthermore, some games existed in multiple versions, e.g. one for Windows and one for Mac OS X. In that case, you may have to detect and distinguish these versions and employ differnt reading calls, to compensate for endian differences in the game data files. | ||
== Struct packing == | == Struct packing == | ||