ObjFW  History of src/encodings/codepage-858.m of c4600793bc0eb21aa94ef95689475d844d4a85908663afb66278d243d2cd1785

In order to not accidentally have C strings with \0, an
OFInvalidEncodingException is thrown when trying to get a C string for a
string that contains \0.

In order to get a C string with \0 anyway, a new method
-[insecureCStringWithEncoding:] is added. file: [2c6eb1a5f6] check-in: [6fbc3b18c7] user: js, branch: trunk, size: 5616 [annotate] [blame] [check-ins using] [diff]

There is no reliable way to check if C++ already defined those, as Clang
now defines char{16,32}_t even when it is not in C++ 11 mode. So we
cannot check if we are not in C++ 11 and then define them and otherwise
rely on the C++ 11 types. file: [f202674432] check-in: [505137f25f] user: js, branch: trunk, size: 5362 [annotate] [blame] [check-ins using] [diff]

This also removes page.*Size, as the macros can just use sizeof() on the
arrays. file: [b4148204c6] check-in: [405d11522e] user: js, branch: trunk, size: 5341 [annotate] [blame] [check-ins using] [diff]