ObjFW  History of src/exceptions/OFMutexLockFailedException.h of fb515e8e242097f5700fe20440a0028d31fa3e86a348d1bdbf42effac5861e6d

History of the file that is called src/exceptions/OFMutexLockFailedException.h at check-in fb515e8e242097f5700fe20440a0028d31fa3e86a348d1bdbf42effac5861e6d

2012-10-26
11:23
Deleted: Add OFLocking protocol. check-in: [7c33158c22] user: js, branch: trunk, size: 0
2012-10-09
15:07
Make use of instancetype. file: [2b5e9d9241] check-in: [fb515e8e24] user: js, branch: trunk, size: 1481 [annotate] [blame] [check-ins using] [diff]
2012-10-02
11:00
Clean up properties in exceptions. file: [bbc20b35d1] check-in: [c7adbcf399] user: js, branch: trunk, size: 1467 [annotate] [blame] [check-ins using] [diff]
2012-02-01
13:42
Clean up the properties mess. file: [a3226afc0e] check-in: [c1b35e1495] user: js, branch: trunk, size: 1456 [annotate] [blame] [check-ins using] [diff]
2012-01-05
00:56
Update copyright. file: [81e8398fba] check-in: [ce70e17b38] user: js, branch: trunk, size: 1459 [annotate] [blame] [check-ins using] [diff]
2011-09-22
23:25
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. file: [5800b9b1cb] check-in: [e1e7ffa903] user: js, branch: trunk, size: 1453 [annotate] [blame] [check-ins using] [diff]

2011-03-25
15:22
Pass the mutex for mutex exceptions. file: [83c96b5ca9] check-in: [343e80e785] user: js, branch: trunk, size: 1441 [annotate] [blame] [check-ins using] [diff]
2011-03-24
16:09
Added: Split OFExceptions.{h,m} into one file per exception. file: [e97a79c3e6] check-in: [e1eea29286] user: js, branch: trunk, size: 699 [annotate] [blame] [check-ins using]