ObjFW  History of src/OFUTF8String.m of 1f32e5e17c6f1a3505efee1ebe8512b9b9d584f5be0714b52c06f31a0ebebecf

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: [731d0242b9] check-in: [6fbc3b18c7] user: js, branch: trunk, size: 30856 [annotate] [blame] [check-ins using] [diff]

Initially, isUTF8 was set to true for all custom string classes because
having isUTF8 set to false was merely an optimization. However,
-[OFUTF8String cStringWithEncoding: OFStringEncodingASCII] throws an
exception when isUTF8 is true. file: [3e5753e6f2] check-in: [cacfcf1b9d] user: js, branch: 1.1, size: 28630 [annotate] [blame] [check-ins using] [diff]

Initially, isUTF8 was set to true for all custom string classes because
having isUTF8 set to false was merely an optimization. However,
-[OFUTF8String cStringWithEncoding: OFStringEncodingASCII] throws an
exception when isUTF8 is true. file: [eb22322b98] check-in: [82c5846734] user: js, branch: trunk, size: 29042 [annotate] [blame] [check-ins using] [diff]

The new names should be more accurate. file: [4b2268ed9f] check-in: [627511b032] user: js, branch: trunk, size: 28421 [annotate] [blame] [check-ins using] [diff]

In particular, this means that if initialization fails, the buffer is
NOT free'd. While freeing it on error in convenient when not handling
the error, it makes handling the error and retrying impossible (e.g.
retrying with a different encoding). file: [e04f7e1202] check-in: [0f260e0fd5] user: js, branch: trunk, size: 28345 [annotate] [blame] [check-ins using] [diff]

The internal hash is still 32 bit in most places, but this way, it is at
least not baked into the API and ABI and can be upgraded later, should
that ever be necessary. file: [d8b3a6972a] check-in: [aeb403a1ed] user: js, branch: trunk, size: 28429 [annotate] [blame] [check-ins using] [diff]