ObjFW  History of src/exceptions/OFBindSocketFailedException.h of c5f91347e72528ad

Instead, explicitly declare them, as OF_ASSUME_NONNULL_{BEGIN,END} does
not apply to implicit return types. This means that after this commit,
all init methods have a nonnull return type, as they should have. file: [289285d273] check-in: [2f4e0df8be] user: js, branch: trunk, size: 2393 [annotate] [blame] [check-ins using] [diff]

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

This changes retaining behavior, meaning properties are not returned
retained and autoreleased anymore, so a property returned from a getter
now needs to be manually retained and autoreleased before calling the
setter. However, this is rarely the case and not using atomic improves
performance. file: [8704ec525d] check-in: [0a73af49f0] user: js, branch: trunk, size: 2186 [annotate] [blame] [check-ins using] [diff]

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

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

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

This increases the required GCC version from 4.0 to 4.6 (exception:
Apple GCC, which already supports this with >= 4.0 starting with OS X
10.5). Since even GCC 4.6 is really old by now, there is no point in
still supporting something even older and making the code ugly because
of that. While some hardware and OS support was dropped from GCC 4.6
compared to GCC 4.0, there is nothing in there that would be an
interesting target with the exception of BeOS maybe - but a port to BeOS
can also be achieved using the Haiku support. The other dropped OSes are
mostly old versions of OSes while newer ones are still being supported
(and those newer versions of those OSes still support the same
hardware). file: [3bc37aa6da] check-in: [48980f2297] user: js, branch: trunk, size: 2168 [annotate] [blame] [check-ins using] [diff]

The old behaviour where the exception would access errno directly on
creation of the exception was very fragile. The two main problems with
it were that sometimes it would pick up an errno even though none had
been set and in other cases that when the exception was created errno
had already been overridden.

This also greatly increases errno handling on Win32, especially in
conjunction with sockets. It can still be improved further, though. file: [e8368795dc] check-in: [62e2de30b9] user: js, branch: trunk, size: 2511 [annotate] [blame] [check-ins using] [diff]

This is in preparation for adding UDP sockets, as UDP sockets and TCP
sockets have no common superclass, as one is stream-oriented while the
other is packet-oriented.

Read and write exceptions are for any object now, as they are useful for
a lot more than just for streams, while the others (bind, listen, etc.)
are for any socket now (the type is id in this case, though, as there is
no common superclass). file: [e51e2f0116] check-in: [8d2a5052fd] user: js, branch: trunk, size: 2306 [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: [8e4f2bb116] check-in: [3d16a30f41] user: js, branch: trunk, size: 2383 [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: [4b614bf39c] check-in: [e1e7ffa903] user: js, branch: trunk, size: 2138 [annotate] [blame] [check-ins using] [diff]