ObjFW  All files named "src/OFSocket.m"

MorphOS has the header, but it's broken and including it makes the
compiler fail. file: [d36d90a400] check-in: [6235989999] user: js, branch: trunk, size: 27529 [annotate] [blame] [check-ins using] [diff]

For some strange reason, Windows does not use big endian here like
everyone else. file: [da4b96c1d5] check-in: [4571eada47] user: js, branch: trunk, size: 25851 [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: [d0ea6d0ea9] check-in: [a54730b88f] user: js, branch: trunk, size: 22894 [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: [b9058d4f4d] check-in: [ccc6a77c55] user: js, branch: trunk, size: 22537 [annotate] [blame] [check-ins using] [diff]

This doesn't work yet (it crashes on recvfrom), so it's not enabled in
configure for now. file: [16116f3ca3] check-in: [a30a0ab261] user: js, branch: nintendo-switch, size: 22537 [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: [9c27c4838b] check-in: [70874cf3c5] user: js, branch: trunk, size: 2951 [annotate] [blame] [check-ins using] [diff]