ObjFW  History of src/exceptions/OFReadFailedException.m of 2cb48ceaf1d0c54a929080b17bcf0f994335809830ae6d0cbd8ae81dc9f2644b

This implements OFTLSStream using Apple's Secure Transport. While Secure
Transport is declared deprecated by Apple, Apple so far has failed to
provide a suitable replacement. They recommend Network.framework as a
replacement, however it can neither work on arbitrary sockets, nor can
it do STARTTLS. file: [2c0f1f9618] check-in: [112eb62f7b] user: js, branch: trunk, size: 1002 [annotate] [blame] [check-ins using] [diff]

This removes several initializers that omitted the errNo. Removing those
forces to think about whether there is a meaningful errNo to set instead
of just omitting it. file: [07f395fcc4] check-in: [4f36894ce7] user: js, branch: trunk, size: 893 [annotate] [blame] [check-ins using] [diff]

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

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

While at it, also update the mail address. file: [d3f619ef44] check-in: [2a27cf3000] user: js, branch: trunk, size: 1054 [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: [700fd5671f] check-in: [62e2de30b9] user: js, branch: trunk, size: 1050 [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: [47786b607d] check-in: [8d2a5052fd] user: js, branch: trunk, size: 890 [annotate] [blame] [check-ins using] [diff]

Also adds a few imports and removes unused code. file: [4d3cf35e83] check-in: [6192726d32] user: js, branch: trunk, size: 902 [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: [5b0d85c885] check-in: [3d16a30f41] user: js, branch: trunk, size: 881 [annotate] [blame] [check-ins using] [diff]

This was pretty pointless, as it's usually only used once. file: [310691b3aa] check-in: [d9ddc4d06e] user: js, branch: trunk, size: 863 [annotate] [blame] [check-ins using] [diff]