NNG_STR_SOCKADDR(3)

💖 NNG_STR_SOCKADDR(3) 💖

okay bestie, welcome to the NNG Reference Manual ✨ you're literally about to learn how to turn a socket address into something your eyeballs can actually read. no cap.

---

🌸 NAME 🌸

nng_str_sockaddr — get the string representation of a socket address 💅

---

🦋 SYNOPSIS 🦋

#include <nng/nng.h>

#define NNG_MAXADDRSTRLEN (NNG_MAXADDRLEN+16)
const char *nng_str_sockaddr(const nng_sockaddr *sa, char *buf, size_t bufsz)

---

✨ DESCRIPTION ✨

so like, nng_str_sockaddr() is the glow-up function 🫶 — it takes the socket address sa and gives you a displayable representation of it. the content gets stored at the location you handed over in buf, and it's formatted to fit inside bufsz bytes. if it doesn't fit? it gets truncated. sad but true 😭

as long as bufsz is greater than zero, the result is gonna be properly zero-terminated in the usual fashion, so don't even stress about that part 💖

NNG_MAXADDRSTRLEN exists so you can make a buffer big enough to hold most socket addresses. and yes, technically applications can use very much larger socket addresses (like, very long paths for IPC or inproc 👀), but heads up — those addresses are not generally compatible with other implementations, and they'll get truncated right here. it's giving "you can do it but why would you" 💀

---

🎀 RETURN VALUES 🎀

this function returns the buf argument. that's it, that's the whole return value. iconic behavior honestly 👑

---

🌈 ERRORS 🌈

None. not a single one. she doesn't do errors, she does vibes ✨

---

💜 SEE ALSO 💜

• nng_sockaddr(5)

---

that's the whole page bestie, go forth and stringify those sockaddrs 🧚‍♀️

— NNG Reference Manual, dated 2026-06-30 💌 mwah, slay, periodt 💅