NNG_MSG_TRIM(3)

✨ NNG_MSG_TRIM 💖

okay bestie so this is a page from the NNG Reference Manual, and it's all about nng_msg_trim — the function family that yeets bytes off the front of a message. no cap. 🎀

---

💅 NAME

nng_msg_trim — remove data from start of message body 🧚

---

🦋 SYNOPSIS

#include <nng/nng.h>

int nng_msg_trim(nng_msg *msg, size_t size);
int nng_msg_trim_u16(nng_msg *msg, uint16_t *val16);
int nng_msg_trim_u32(nng_msg *msg, uint32_t *val32);
int nng_msg_trim_u64(nng_msg *msg, uint64_t *val64);

---

🌸 DESCRIPTION

okay so picture this: you've got a message, and its body has stuff at the start that you don't want anymore. the nng_msg_trim() family of functions removes data from the start of the body of message msg. it's giving "scissors but for buffers". ✂️✨

here's the breakdown, bestie:

• the first function, nng_msg_trim(), removes size bytes. that's it. that's the whole job. 👑
• the remaining functions remove 2, 4, or 8 bytes respectively, and — plot twist — they store those bytes in the value (such as val32) after converting them from network-byte order (big-endian) to native byte order. so you're not just trimming, you're also decoding. main character energy fr fr. 🌈

---

💖 RETURN VALUES

these functions return 0 on success, and non-zero otherwise. simple as. 🫶

---

🚨 ERRORS

• NNG_EINVAL — the message body is too short to remove the requested data. like?? you can't trim what isn't there bestie 😭 the vibe check failed, the body simply does not have enough bytes.

---

👀 SEE ALSO

• nng_msg_alloc(3)
• nng_msg_append(3)
• nng_msg_body(3)
• nng_msg_chop(3)
• nng_msg_free(3)
• nng_msg_insert(3)
• nng_msg_len(3)
• nng_msg_realloc(3)
• nng_strerror(3)
• nng_msg(5)
• nng(7)

---

and that's the whole page, babe — literally every detail, none skipped, no crumbs left behind 💜

this lil masterpiece comes to you courtesy of the NNG Reference Manual, dated 2026-06-30. that's the source, that's the version, that's the date. periodt. 💅✨🎀