ObjFW  History of src/OFString_UTF8.m of dbfe400f6eadce14

This is the first step to have different versions of those for different
operating systems, rather than #ifdefs everywhere.

This also has the nice side-effect of not having one implementation in
OFString and another one in OFString_UTF8 anymore. The one in OFString
was a generic version, while the one in OFString_UTF8 was one optimized
for UTF-8 strings. Now only the version optimized for UTF-8 strings
exists, as this is by far the most common string implementation used,
and the overhead of converting from something else to UTF-8 is not more
than converting to UTF-32. file: [ec2d5729ba] check-in: [7a488c3062] user: js, branch: trunk, size: 28455 [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: [d6a602d281] check-in: [505137f25f] user: js, branch: trunk, size: 30558 [annotate] [blame] [check-ins using] [diff]

Since OFComparing no longer conforms to OFObject, OFObject needed to be
added at a few places. file: [879030fae2] check-in: [11f24addd7] user: js, branch: trunk, size: 30490 [annotate] [blame] [check-ins using] [diff]

This also adds -[OFURL fileSystemRepresentation] to correctly convert a
URL back to a path in the local file system. file: [c30817026a] check-in: [b83d1414b1] user: js, branch: trunk, size: 30176 [annotate] [blame] [check-ins using] [diff]

Instead, explicitly declare them, as OF_ASSUME_NONNULL_{BEGIN,END} does
not apply to implicit return types. This means that after this commit,
all init methods have a nonnull return type, as they should have. file: [3425587555] check-in: [2f4e0df8be] user: js, branch: trunk, size: 30509 [annotate] [blame] [check-ins using] [diff]

This matches Apple's style. file: [2b39181352] check-in: [6b77a5dd8b] user: js, branch: trunk, size: 30355 [annotate] [blame] [check-ins using] [diff]

Casts are now written like types in variable declarations. file: [fc310b0712] check-in: [4af49a13c3] user: js, branch: trunk, size: 30406 [annotate] [blame] [check-ins using] [diff]

This allows building a smaller ObjFW if those are not needed. file: [652cb8ee2f] check-in: [766eedef4c] user: js, branch: trunk, size: 29405 [annotate] [blame] [check-ins using] [diff]

This only differs from codepage 850 by a single code point. file: [f5ba43aeaa] check-in: [adbf31f2f9] user: js, branch: trunk, size: 29036 [annotate] [blame] [check-ins using] [diff]

This used to be U+FFFD, but if a character is not assigned in an
encoding, U+FFFF is a better match. file: [38f6296657] check-in: [a9f85ba3b1] user: js, branch: trunk, size: 28786 [annotate] [blame] [check-ins using] [diff]

Forgot to add 2017, even though I already did quite some changes in
2017. file: [432a4769a5] check-in: [44f45c2e35] user: js, branch: trunk, size: 28545 [annotate] [blame] [check-ins using] [diff]

These are independent of the locale and work on the ASCII character set.

Unlike the C ones, these are 8-bit safe, meaning if a character > 0x7F
is passed, is{alpha,alnum} returns false and to{upper,lower} returns the
original character. file: [b0d3c841b5] check-in: [d9eb7b50b3] user: js, branch: trunk, size: 28539 [annotate] [blame] [check-ins using] [diff]

This is only useful for size-constrained systems and changes the
behavior as follows:

* Case-insensitive comparisons only work as expected for ASCII
characters. This means that while a and A compare equal, ä and Ä do
not.

* -[OFMutableString {upper,lower}] and
-[OFString {upper,lower}caseString] only work on ASCII characters;
all other characters are left as they are. This means that the upper
version of a is A, but the upper version of ä is still ä (and vice
versa for lower). file: [539d29c205] check-in: [b7b33247d6] user: js, branch: trunk, size: 28512 [annotate] [blame] [check-ins using] [diff]

This is required as passing something signed to it is an error on
NetBSD, but passing anything else than a char is undefined on Linux. file: [f214cc2fb6] check-in: [09a0d12bae] user: js, branch: trunk, size: 28142 [annotate] [blame] [check-ins using] [diff]

It now returns <= 0 on error, with negative values being the number of
bytes it would have needed * -1.

This can be used to detect cut off and how many bytes are missing. file: [c460dbfe91] check-in: [5e2ef97c35] user: js, branch: trunk, size: 28090 [annotate] [blame] [check-ins using] [diff]

While at it, also update the mail address. file: [035a617a1b] check-in: [2a27cf3000] user: js, branch: trunk, size: 28015 [annotate] [blame] [check-ins using] [diff]

This means that OFObject.h imports macros.h now, making it unnecessary
to manually import macros.h in almost every file. And while at it, also
import autorelease.h in OFObject.h, so that this doesn't need to be
manually imported in almost every file as well. file: [60dc6c49fb] check-in: [13ee56edf3] user: js, branch: trunk, size: 27876 [annotate] [blame] [check-ins using] [diff]

No functional change intended. file: [26025dccab] check-in: [9da9b2b64c] user: js, branch: trunk, size: 27919 [annotate] [blame] [check-ins using] [diff]

The port was much easier than expected. The only changes that were
required were defining the missing lrint() and useconds_t, the rest was
optional (like using backslashes for paths, even though slashes work
fine). file: [458af69b3f] check-in: [a0b63a8df4] user: js, branch: trunk, size: 28773 [annotate] [blame] [check-ins using] [diff]

This removes -[initWithPath:,...], so that it's finally possible to use
-[initWithPath:] for many places where a workaround like
-[initWithDirectoryPath:] was required before. file: [dcb1103ce6] check-in: [7c4179ab9b] user: js, branch: trunk, size: 28846 [annotate] [blame] [check-ins using] [diff]

This is required for ZIP files, which can use either codepage 437 or
Unicode. file: [48ca6830d9] check-in: [3912669d91] user: js, branch: trunk, size: 30410 [annotate] [blame] [check-ins using] [diff]

This mostly removes the argument for the class in which the exception
occurred. As backtraces were recently added for all platforms, the
passed class does not give any extra information on where the exception
occurred anymore.

This also removes a few other arguments which were not too helpful. In
the past, the idea was to pass as many arguments as possible so that it
is easier to find the origin of the exception. However, as backtraces
are a much better way to find the origin, those are not useful anymore
and just make the exception more cumbersome to use. The rule is now to
only pass arguments that might help in recovering from the exception or
provide information that is otherwise not easily accessible. file: [3a479b89af] check-in: [3d16a30f41] user: js, branch: trunk, size: 30279 [annotate] [blame] [check-ins using] [diff]

The only places where BOOL is left are those where they are required by
the ABI. file: [3ce37a1895] check-in: [c5ef582958] user: js, branch: trunk, size: 31231 [annotate] [blame] [check-ins using] [diff]

For ObjC++, these are defined to char{16,32}_t if C++11 is used. This
means passing e.g. a C++11 UTF-16 string to -[initWithUTF16String:]
works without a warning.

For C11, this is not necessary, as char{16,32}_t are just typedef'd to
uint_least{16,32}_t in <uchar.h> and thus compatible to the definition
of of_char{16,32}_t. The reason for not defining of_char{16,32}_t to
char{16,32}_t when using C11 is that <uchar.h> might be missing and that
char{16,32}_t are not required to be UTF-{16,32}, whereas in C++, they
are required to be UTF-{16,32}. file: [5a1fe9d9fc] check-in: [545b6f740e] user: js, branch: trunk, size: 30912 [annotate] [blame] [check-ins using] [diff]

This reverts 5362941.

Even though *UsingEncoding: is what Foundation uses, *WithEncoding: is
more natural and is more consistent with the rest. Also, this means this
restores it to the API of 0.7. file: [c16c78a6d7] check-in: [9ddd33a258] user: js, branch: trunk, size: 30900 [annotate] [blame] [check-ins using] [diff]

With this change, there is a clear separation between characters and
UTF-32 strings now. Characters are just an array of characters in the
native endianess, with no BOM prepended. UTF-32 on the other hand may
have a BOM and can be swapped and is optionally zero-terminated.

This also fixes a few missing UTF-16 init methods in OFMutableString. file: [97c02a6c42] check-in: [50916b8dbe] user: js, branch: trunk, size: 30904 [annotate] [blame] [check-ins using] [diff]

* Instead of Unicode "strings", it uses the term "Unicode character
array".
* No terminating 0 character anymore, as these are not C strings
anyway. file: [797a478d4d] check-in: [640b225ba7] user: js, branch: trunk, size: 28916 [annotate] [blame] [check-ins using] [diff]

This adds ISO 8859-1 and ASCII, ISO 8859-15 and Windows-1252 will
follow. file: [75ce5faed6] check-in: [556234e290] user: js, branch: trunk, size: 30422 [annotate] [blame] [check-ins using] [diff]

This should make it more future-proof, as adding new options is easier
than adding new methods for each and every combination of options. file: [7a3937da16] check-in: [fcaa549324] user: js, branch: trunk, size: 30604 [annotate] [blame] [check-ins using] [diff]

This makes it clear that multiple evaluation of parameters is possible. file: [2e4dae0bbe] check-in: [1cb8fee5c3] user: js, branch: trunk, size: 29614 [annotate] [blame] [check-ins using] [diff]

This greatly improves performance, as it gets rid of the overhead of
OFAutoreleasePool. file: [b0a0f37ea8] check-in: [1255f3a11a] user: js, branch: trunk, size: 25451 [annotate] [blame] [check-ins using] [diff]

Also fix a bug where OFBigDataArray would waste memory. file: [5faa6d539b] check-in: [f7576a66ce] user: js, branch: trunk, size: 25150 [annotate] [blame] [check-ins using] [diff]

A linked-list is put before each memory chunk allocated instead of
having an array of all memory chunks. This means only one malloc now
instead of one malloc and one realloc. This also means that when
checking reallocs and frees, it's no longer necessary to iterate through
all memory chunks, as the linked list also contains the owner, meaning
realloc and free are no longer O(n), but O(1) now.

As allocating bigger chunks seems to be a little bit slower than smaller
chunks, it seems that this is slightly slower in benchmarks if only very small
chunks are allocated. However, measuring real world usage, it's a lot faster. file: [2df9fbd0df] check-in: [28170f5f65] user: js, branch: trunk, size: 24829 [annotate] [blame] [check-ins using] [diff]

It is a class cluster now, but there is still much to improve. file: [3609f3a164] check-in: [301ee63212] user: js, branch: trunk, size: 23880 [annotate] [blame] [check-ins using]