ObjFW  History of src/OFStreamSocket.m of 9a6b5d6cc44f538a

On game consoles, initializing sockets takes a significant amount of
time. When not delaying socket initializing, that time is spent during
startup even when the application might never use sockets.

Worse yet, on Amiga, sockets might not be available at all and the
application will fail to start up, even when the application might never
use sockets. file: [6bb8a2cf49] check-in: [7460d2ccd8] user: js, branch: trunk, size: 10099 [annotate] [blame] [check-ins using] [diff]

It doesn't seem to be needed anymore. file: [a2d2d261a8] check-in: [cf0effe834] user: js, branch: trunk, size: 9921 [annotate] [blame] [check-ins using] [diff]

This uses the same format as OFEnsure(). file: [21ea0af8b5] check-in: [c86b8f10f0] user: js, branch: trunk, size: 8562 [annotate] [blame] [check-ins using] [diff]

struct sockaddr can contain a variable length array, which breaks the
union. file: [6c817945cd] check-in: [25adea9a23] user: js, branch: trunk, size: 8540 [annotate] [blame] [check-ins using] [diff]

This is more standard, albeit -[connectToNetwork:node:port:] sounding a
little bit more like you connect to a network rather than a node. file: [aac8571961] check-in: [ccc6a77c55] user: js, branch: trunk, size: 8489 [annotate] [blame] [check-ins using] [diff]

There is a nasty bug in HP-UX: When using the proper socket APIs that
take a socklen_t (which is 64 bit in LP64 mode), it still calls into
methods that expect an int - so there is a type mismatch between the
headers and the compiled system libraries. This leads to all socklen_t
being interpreted as 0 (due to big endian). Defining
_HPUX_ALT_XOPEN_SOCKET_API makes it use the correct symbols in the
system libraries instead. file: [791405f855] check-in: [1833194867] user: js, branch: trunk, size: 8364 [annotate] [blame] [check-ins using] [diff]

This is intended for SCTP and SPX. file: [53952137a2] check-in: [e5b2ee56ff] user: js, branch: trunk, size: 4323 [annotate] [blame] [check-ins using] [diff]

This makes it easier to reuse code for other datagram sockets, namely
IPX. file: [3d9d6aa117] check-in: [b02c4b05bb] user: js, branch: trunk, size: 4333 [annotate] [blame] [check-ins using] [diff]

Closing them in OFStream would result in always canceling them after
closing the socket due to the -[close] chaining - which could never
work. file: [6026b8fcfc] check-in: [cea3f2133d] user: js, branch: trunk, size: 4136 [annotate] [blame] [check-ins using] [diff]

This allows retrieving the number of bytes already written before the
write failed, allowing to retry without writing data that has already
been written. file: [272212f745] check-in: [2ae01218ef] user: js, branch: trunk, size: 4073 [annotate] [blame] [check-ins using] [diff]

Instead, let reads return 0 and let writes append after the end. file: [eec652ecb7] check-in: [f9cd4f9cab] user: js, branch: trunk, size: 3785 [annotate] [blame] [check-ins using] [diff]

Previously, socket_helpers.h would just define close() to whatever is
needed to close a socket. However, this makes it possible to
accidentally call a socket-specific close on something that is not a
socket. Having to explicitly call closesocket() (and defining it to
close() on platforms where it's the same) prevents this. file: [c248fb563e] check-in: [b4cd87cd81] user: js, branch: trunk, size: 3980 [annotate] [blame] [check-ins using] [diff]

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

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

Right now, this is only useful for OFTCPSocket, as this is the only
class so far not establishing the stream in the init method. However,
this adds the general infrastructure to allow reuse to all subclasses of
OFStream. file: [77a66a4df1] check-in: [1de551cb5f] user: js, branch: trunk, size: 3966 [annotate] [blame] [check-ins using] [diff]

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

While at it, also update the mail address. file: [3021941e31] check-in: [2a27cf3000] user: js, branch: trunk, size: 3949 [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: [c547367b26] check-in: [62e2de30b9] user: js, branch: trunk, size: 3777 [annotate] [blame] [check-ins using] [diff]

LLP64 was mostly fast enumeration using an unsigned long for the state,
which can't store a pointer or a size_t on LLP64. This is now solved by
either throwing an OFOutOfRangeException if the value of the size_t is
bigger than ULONG_MAX or storing the pointer in the extra field (copied
using memcpy, as it's an array of unsigned long, which again would be
too small to store a pointer).

Win64 was mostly Microsoft not being able to decide whether a length is
a size_t, a DWORD, an int or an unsigned int (thus the different types
in places that seem to be almost the same). But since that would not be
confusing enough, a file descriptor is an int if it's for a file, but a
long long if it is for a socket. But of course, for ReadFile and friends
it's a DWORD instead of an int then. file: [43c1e24000] check-in: [4e59d2692f] user: js, branch: trunk, size: 3691 [annotate] [blame] [check-ins using] [diff]

The new file socket.h includes all headers required for sockets on the
used platform, while the file socket_helpers.h defines the BSD API
functions to the platform specific functions if necessary.

This cleans up the classes dealing with sockets a lot and also reduces
code duplication. file: [c2425f91c0] check-in: [81d47f4398] user: js, branch: trunk, size: 3129 [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: [5b827e504d] check-in: [8d2a5052fd] user: js, branch: trunk, size: 3523 [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: [252939c90a] check-in: [3d16a30f41] user: js, branch: trunk, size: 3629 [annotate] [blame] [check-ins using] [diff]

Not functional yet due to bugs in the SDK.
Bugs found so far:

* Binding to port 0 fails instead of choosing a free port.
* gethostbyname() does not work for IPs.
* getsockname() is missing.
* struct sockaddr_storage is missing.

I have not decided yet whether I fix those bugs in the SDK (I already
implemented getsockname() and added struct sockaddr_stroage and it seems
to work) or if I work around them in ObjFW. This will mainly depend on
how cooperative the developers of the Wii SDK are. file: [10e23bfd72] check-in: [ffb91daffe] user: js, branch: trunk, size: 3874 [annotate] [blame] [check-ins using] [diff]

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

It is now -[fileDescriptorForReading] and -[fileDescriptorForWriting].
The split was necessary as some stream types (e.g. OFProcess) don't have
a single file descriptor, but two. This allows to use those stream types
with OFStreamObserver as well. file: [fbc78fae5c] check-in: [440e95fd4a] user: js, branch: trunk, size: 3409 [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: [45578e9a1c] check-in: [e1e7ffa903] user: js, branch: trunk, size: 3273 [annotate] [blame] [check-ins using] [diff]

Without this, the headers try to declare functions that use __block as
an argument name and thus fail to compile when using -fblocks. file: [49fed451d1] check-in: [59e52af26d] user: js, branch: 0.5, size: 3159 [annotate] [blame] [check-ins using] [diff]

Without this, the headers try to declare functions that use __block as
an argument name and thus fail to compile when using -fblocks. file: [73e9748565] check-in: [da2701ad14] user: js, branch: trunk, size: 3296 [annotate] [blame] [check-ins using] [diff]

This is to reflect that it is a connection-based, sequenced, reliable,
two-way byte stream. file: [1c776793df] check-in: [28ea4a8a67] user: js, branch: trunk, size: 2343 [annotate] [blame] [check-ins using]