ObjFW  All files named "src/OFString+CryptoHashing.m"

This makes it clearer that these return a string and not a hash object. file: [e8341b8291] check-in: [b5a74319e1] user: js, branch: trunk, size: 2354 [annotate] [blame] [check-ins using] [diff]

With this property, it's possible to specify whether the memory should
be protected from swapping or not. This makes it easier for e.g. the
crypto hash classes: They can now just always use OFSecureData without
wasting unswappable memory if it's not needed. file: [2bc09b0ad0] check-in: [e629dc83a9] user: js, branch: trunk, size: 2366 [annotate] [blame] [check-ins using] [diff]

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

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

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

While in practice they are usually the same, the C standard says that
only char does not have any alignment requirements. As (u)int*_t is
defined to be an integer type of the specified size, it does not mean
(u)int8_t needs to be char. file: [fc8a2533b9] check-in: [19f7dc67af] user: js, branch: trunk, size: 2293 [annotate] [blame] [check-ins using] [diff]

OFHash is too generic, as this protocol is for cryptographic hashes. It
also solves the ambiguity of the +[hash] method (which is now
+[cryptoHash]), which conflicted with -[hash] on the class itself,
resulting in classes conforming to OFHash not being able to be used as a
key in an OFDictionary. file: [73f20bd87d] check-in: [951f530aee] user: js, branch: trunk, size: 2287 [annotate] [blame] [check-ins using]