ObjFW  History of src/exceptions/OFNotConnectedException.m of 06251136e541cf9c

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: [3dd688e897] check-in: [62e2de30b9] user: js, branch: trunk, size: 1195 [annotate] [blame] [check-ins using] [diff]

This means that OFObject.h imports macros.h now, making it unnecessary
to manually import macros.h in almost every file. And while at it, also
import autorelease.h in OFObject.h, so that this doesn't need to be
manually imported in almost every file as well. file: [32f81be35f] check-in: [13ee56edf3] user: js, branch: trunk, size: 1209 [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: [916c8267e0] check-in: [8d2a5052fd] user: js, branch: trunk, size: 1228 [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: [4793cd3e58] check-in: [3d16a30f41] user: js, branch: trunk, size: 1376 [annotate] [blame] [check-ins using] [diff]

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

This was pretty pointless, as it's usually only used once. file: [096c56ad4d] check-in: [d9ddc4d06e] user: js, branch: trunk, size: 1471 [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: [564baa5da5] check-in: [e1e7ffa903] user: js, branch: trunk, size: 1527 [annotate] [blame] [check-ins using] [diff]