ObjFW  History of src/exceptions/OFDeleteFileFailedException.m of e7d16fea587a5ad6

Also adds a few imports and removes unused code. file: [742ec5f1c5] check-in: [6192726d32] user: js, branch: trunk, size: 1451 [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: [889f5dd334] check-in: [3d16a30f41] user: js, branch: trunk, size: 1416 [annotate] [blame] [check-ins using] [diff]

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

This was pretty pointless, as it's usually only used once. file: [443055fc12] check-in: [d9ddc4d06e] user: js, branch: trunk, size: 1556 [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: [046ff78fb5] check-in: [e1e7ffa903] user: js, branch: trunk, size: 1624 [annotate] [blame] [check-ins using] [diff]