ObjFW  All files named "src/OFSocket.h"

It seems that neither Windows nor macOS support DDP sockets, but only
the layers on top, while neither Linux nor NetBSD support the layers on
top, but only provide DDP.

It seems that DDP is not meant to be used directly, while Linux and
NetBSD only provide the minimum to use netatalk, which is DDP. ObjFW
would need to use the layers on top on Windows and macOS and implement
those layers itself on Linux and NetBSD. This also means that no code
would be shared between Linux / NetBSD and Windows / macOS, as it's
impossible to have one implementation that works for everything. At this
point, the effort required doesn't make sense. file: [fc6ec6273c] check-in: [0b4f713964] user: js, branch: trunk, size: 9155 [annotate] [blame] [check-ins using] [diff]

While it works for those two protocols, it's a bad precedent as other
protocols have different types for ports. file: [e6bf54de5e] check-in: [a54730b88f] user: js, branch: trunk, size: 9155 [annotate] [blame] [check-ins using] [diff]

struct sockaddr can contain a variable length array, which breaks the
union. file: [0929d955af] check-in: [25adea9a23] user: js, branch: trunk, size: 8480 [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: [e523ef42af] check-in: [ccc6a77c55] user: js, branch: trunk, size: 8749 [annotate] [blame] [check-ins using] [diff]

Windows 10 supports UNIX sockets since Insider Preview Build 17063, but
only SOCK_STREAM. file: [65bba562bd] check-in: [d5373ff70f] user: js, branch: unix-sockets, size: 8733 [annotate] [blame] [check-ins using] [diff]

With TYPEDEF_HIDES_STRUCT set, Doxygen properly handles anonymous
structs and enums that are typedef'd. file: [2b4aae9d25] check-in: [2fcf5a3052] user: js, branch: trunk, size: 7772 [annotate] [blame] [check-ins using] [diff]

This is to reflect that it is a connection-based, sequenced, reliable,
two-way byte stream. check-in: [28ea4a8a67] user: js, branch: trunk, size: 0

Endianess, size etc. may differ from system to system. While this might
be ok when writing files that are only read local again, this is
definitely not ok with sockets. So it's better to remove it from the
OFStream protocol. file: [e31807ae92] check-in: [70874cf3c5] user: js, branch: trunk, size: 2917 [annotate] [blame] [check-ins using] [diff]