ObjFW  History of src/OFXMLElement+Serialization.m of 5a6cc94418ebec9d

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

While at it, also update the mail address. file: [306536eaaf] check-in: [2a27cf3000] user: js, branch: trunk, size: 1323 [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: [9f69c54430] check-in: [13ee56edf3] user: js, branch: trunk, size: 1313 [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: [6b31560ec3] check-in: [3d16a30f41] user: js, branch: trunk, size: 1351 [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: [ccf852396a] check-in: [9ddd33a258] user: js, branch: trunk, size: 1408 [annotate] [blame] [check-ins using] [diff]

This greatly improves performance, as it gets rid of the overhead of
OFAutoreleasePool. file: [2f13ccd9ab] check-in: [1255f3a11a] user: js, branch: trunk, size: 1472 [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: [5a6af4a224] check-in: [e1e7ffa903] user: js, branch: trunk, size: 1484 [annotate] [blame] [check-ins using] [diff]