ObjFW  History of src/OFString+XMLEscaping.m of 764fe0bac3cc387e

This uses the same format as OFEnsure(). file: [32ead971e3] check-in: [c86b8f10f0] user: js, branch: trunk, size: 2070 [annotate] [blame] [check-ins using] [diff]

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

-[allocMemoryWithSize:] has book keeping overhead that is unnecessary
for temporary memory. file: [e1df224af8] check-in: [0ddaac3f5b] user: js, branch: trunk, size: 2153 [annotate] [blame] [check-ins using] [diff]

While it makes sense to wrap malloc and calloc to replace the error
checking with exceptions, it does not make sense to wrap free. file: [bd600aa82b] check-in: [3d8286feee] user: js, branch: trunk, size: 2235 [annotate] [blame] [check-ins using] [diff]

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

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

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

Those were only a problem if the user created its own OFString subclass,
as calls to -[UTF8String] could then create a new, autoreleased C
string. As OFString_UTF8 simply returns the internal C string, this
hasn't been a problem when not subclassing OFString. file: [fb650f788f] check-in: [b5c8b62533] user: js, branch: trunk, size: 2427 [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: [08aa8faea7] check-in: [3d16a30f41] user: js, branch: trunk, size: 2347 [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: [4bad4e66f4] check-in: [e1e7ffa903] user: js, branch: trunk, size: 2359 [annotate] [blame] [check-ins using] [diff]

This is the only way the \r does not get lost when parsing the XML! file: [aa261c5ddc] check-in: [7d8ab5ba31] user: js, branch: 0.5, size: 2129 [annotate] [blame] [check-ins using] [diff]

This is the only way the \r does not get lost when parsing the XML! file: [bd18e10f31] check-in: [f5f074e27e] user: js, branch: trunk, size: 2261 [annotate] [blame] [check-ins using] [diff]