TCPClientConnection(3)

💖 NAME 💖

TCPClientConnection — bestie, it's the client-side socket vibe from MPQC, and yes it's a 3 page, so it's a library thing, not a command you type into your shell 🫶

---

✨ SYNOPSIS ✨

Okay so the whole family tree situation first, because it's giving inheritance:

Inherits TCPIOSocket.

That's it. That's the lineage. Iconic of it honestly 💅

🎀 Public Member Functions

Here's the full lineup, every single one, no skips:

• void close () — the close () call. Zero arguments, returns void, and it's the one you reach for when you're done-done 🌙
• bool connected () — the connected () call, no arguments, and it hands you back a bool so you can vibe-check the state 🦋
• void connect (const char *remote_hostname, u_int16_t remote_port) — the connect call that takes a const char *remote_hostname and a u_int16_t remote_port. Name-based, cute, very "I know where I'm going" ✨
• void connect (u_int32_t remote_host, u_int16_t remote_port) — the other connect call, and this one takes a u_int32_t remote_host plus a u_int16_t remote_port. Same name, different args, that's overloading and she ate 🔥

Not me pointing out that there are two connect functions with the same name — yes bestie, that's intentional, it's overloaded, don't panic 💀

🌈 Additional Inherited Members

There are also Additional Inherited Members hanging around in here. They come with the territory of inheriting from TCPIOSocket, and they're part of this class's story too, iykyk 👑

---

🌸 AUTHOR 🌸

Generated automatically by Doxygen for MPQC from the source code. So like… nobody hand-wrote this one, the robot did it, and honestly? Respect the automation 🤖💖

---

And that's the whole page, bestie — no cap, every flag, every signature, every section, right where it belongs. This was MPQC, Version 2.3.1, dated Sun Oct 4 2020, and that's the sign-off 💜 🎀 🦋