ObjFW  History of tests/OFListTests.m of 806625744240c74c

ObjFW's style changed over the years, but the tests were never adjusted
to it. file: [8b9464c149] check-in: [14f1e22d79] user: js, branch: trunk, size: 3943 [annotate] [blame] [check-ins using] [diff]

OFAutoreleasePools have long been discouraged in favor of the runtime's
autorelease pools. file: [a93ef64198] check-in: [09be825f88] user: js, branch: trunk, size: 3993 [annotate] [blame] [check-ins using] [diff]

It's not very useful and is a problem for the Foundation bridge, as
NSEnumerator does not have it. file: [0f5664c086] check-in: [7214a2c7af] user: js, branch: trunk, size: 3995 [annotate] [blame] [check-ins using] [diff]

This prevents forgetting to add an import to ObjFW.h, as the tests would
then not compile. file: [a586847fd9] check-in: [dc0c6c34ab] user: js, branch: trunk, size: 4069 [annotate] [blame] [check-ins using] [diff]

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

While at it, also update the mail address. file: [a319eef751] check-in: [cec0f072f8] user: js, branch: 0.8, size: 4176 [annotate] [blame] [check-ins using] [diff]

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

Now that we require GCC >= 4.6, those features are always available. file: [c4bfbb1bc1] check-in: [be8db49635] user: js, branch: trunk, size: 4133 [annotate] [blame] [check-ins using] [diff]

Clang now warns if the enumeration variable of a fast enumeration is not
used. file: [6fc9d88b76] check-in: [6143baaaee] user: js, branch: trunk, size: 4160 [annotate] [blame] [check-ins using] [diff]

The only places where BOOL is left are those where they are required by
the ABI. file: [a1285e945c] check-in: [c5ef582958] user: js, branch: trunk, size: 4139 [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: [ec7c33e58e] check-in: [e1e7ffa903] user: js, branch: trunk, size: 4133 [annotate] [blame] [check-ins using] [diff]