4.3 Types

Various different integer types are used throughout MuPDF.

In general:

• int is assumed to be at least 32 bits.
• short is assumed to be exactly 16 bits.
• char is assumed to be exactly 8 bits.
• array sizes, string lengths, and allocations are measured using size_t. size_t is 32bit in 32bit builds, and 64bit on all 64bit builds.
• buffers of data use unsigned chars (or uint8_t).
• Offsets within files/streams are represented using int64_t on all builds for simplicity.

Previously MuPDF used a fz_off_t type for file offsets. This changed size according to build type or FZ_LARGEFILE being defined, but this has been abandoned due to potential pitfalls. Having the API change between builds according to different symbol definitions is poor form as it can lead to unexpected crashes.

In addition, we use floats (and doubles internally, though we avoid these in the API where possible). These are assumed to be IEEE compliant.