socket_connect4(3)

💖 socket_connect4 — bestie's guide to saying "hey" over TCP 💖

okay so you wanna know about socket_connect4, from the Library Functions Manual, section 3. It's a libowfat thing and honestly? It's giving "let me introduce you to somebody." Sit down, hydrate, let's go. 🫶

---

✨ NAME ✨

socket_connect4 — attempt to make a TCP connection 💅

---

🌸 SYNTAX 🌸

#include <libowfat/socket.h>

int socket_connect4(int s,const char ip[4],uint16 port);

no cap, that's the whole signature. s is your TCP socket, ip is a 4-byte address, port is a uint16. that's it bestie. 🎀

---

🦋 DESCRIPTION 🦋

So like — socket_connect4 attempts to make a connection from TCP socket s to TCP port port on IP address ip. Simple. Iconic. A matchmaker for sockets. 🔥

Now the part you actually need to internalise: socket_connect4 may return a few different things, and each one is a whole mood. 💀

• 0 — this means the connection succeeded, and it succeeded immediately if the socket is non-blocking. slay.
• -1, with errno set to error_inprogress or error_wouldblock — this is the "it's not a no, it's a not-yet" outcome. It means the socket is non-blocking. the connection is still out there doing its thing.
• -1, with errno set to something else — this means the connection failed (and it failed immediately, if the socket is non-blocking). 💔

Heads up bestie: those last two both look like -1 from the outside, so the way you tell "still cooking" apart from "it's over" is by checking errno. Don't skip that step, I'm begging. 🙈

When a background connection succeeds or fails, s becomes writable. So that's your cue to check in. You can use socket_connected to see whether the connection actually succeeded. And if the connection failed, socket_connected returns 0, setting errno appropriately. ✨

Once a TCP socket is connected, you can use the read and write system calls to transmit data. yep, the normal ones. the classics. 👑

And here's a cute lil flex: you can call socket_connect4 without calling socket_bind4. That has the effect as first calling socket_bind4 with IP address 0.0.0.0 and port 0. So like, the universe just handles it for you. 💖

---

🌈 EXAMPLE 🌈

copy this, it's cute:

#include <libowfat/socket.h>

int s;
char ip[4];
uint16 p;

s = socket_tcp4();
socket_bind4(s,ip,p);
socket_connect4(s,ip,p);

---

👑 SEE ALSO 👑

• socket_connect6(3) — for when your bestie has a 128-bit address 🌸
• socket_fastopen_connect4(3) — the speedrun version ⭐

---

okay so that's the whole page, mwah 💜 This one is socket_connect4(3) — section 3 of the Library Functions Manual — and that's genuinely the whole footer situation, no version, no date stamp, so that's the receipt. go forth and connect, bestie, you're gonna eat 💅✨🎀