ObjFW  History of src/exceptions/OFMutexStillLockedException.h of 1e9b75e44dc428dc

History of the file that is called src/exceptions/OFMutexStillLockedException.h at check-in 1e9b75e44dc428dc

2012-10-26
11:23
Deleted: Add OFLocking protocol. (check-in: [7c33158c22] user: js, branch: trunk, size: 0)
2012-10-09
15:07
[ae45a21493] part of check-in [fb515e8e24] Make use of instancetype. (check-in: [fb515e8e24] user: js, branch: trunk, size: 1466) [annotate] [blame] [check-ins using] [diff]
2012-10-02
11:00
[0ff3264cf0] part of check-in [c7adbcf399] Clean up properties in exceptions. (check-in: [c7adbcf399] user: js, branch: trunk, size: 1452) [annotate] [blame] [check-ins using] [diff]
2012-02-01
13:42
[b951acfe65] part of check-in [c1b35e1495] Clean up the properties mess. (check-in: [c1b35e1495] user: js, branch: trunk, size: 1441) [annotate] [blame] [check-ins using] [diff]
2012-01-05
00:56
[a04eab2c6f] part of check-in [ce70e17b38] Update copyright. (check-in: [ce70e17b38] user: js, branch: trunk, size: 1444) [annotate] [blame] [check-ins using] [diff]
2011-09-22
23:25
[33a6088f80] part of check-in [e1e7ffa903] Exceptions are now autoreleased.

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. (check-in: [e1e7ffa903] user: js, branch: trunk, size: 1438) [annotate] [blame] [check-ins using] [diff]

2011-03-25
15:22
Added: [f912b04534] part of check-in [343e80e785] Pass the mutex for mutex exceptions. (check-in: [343e80e785] user: js, branch: trunk, size: 1426) [annotate] [blame] [check-ins using]