ObjFW  History of src/OFObject+Serialization.m of e91cba848b550271

While the idea sounds nice that the tag name is the class, this means the
serialization includes whether something is mutable or immutable. This means
doing as much as making something immutable changes the serialization, which
can then cause issues after being deserialized. check-in: [6ce0093f8d] user: js, branch: trunk, size: 0

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

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

While at it, also update the mail address. file: [6a3c9323c9] check-in: [2a27cf3000] user: js, branch: trunk, size: 1538 [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: [16211d6d3b] check-in: [13ee56edf3] user: js, branch: trunk, size: 1528 [annotate] [blame] [check-ins using] [diff]

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

printf's %a was too fragile to serialize floats and doubles, as it was
behaving differently on different OSes and OS versions. Instead, a hex
representation of the float/double in big endian is used now. While this
is less readable, it is guaranteed to be accurate and always the same. file: [d27599f768] check-in: [a6ee2b2065] user: js, branch: trunk, size: 1643 [annotate] [blame] [check-ins using] [diff]

This is safe as an "exception loop" can't happen, since if allocating
an exception fails, it throws an OFAllocFailedException which is
preallocated and can always be thrown.

So, the worst case would be that an autorelease of an exception fails,
triggering an OFOutOfMemoryException for which there is no memory,
resulting in an OFAllocFailedException to be thrown. file: [f21298cd9d] check-in: [e1e7ffa903] user: js, branch: trunk, size: 1628 [annotate] [blame] [check-ins using] [diff]