ZMQ_MSG_SET(3)

πŸ’– NAME πŸ’–

zmq_msg_set β€” set a message property, bestie. that's literally it πŸŽ€


✨ SYNOPSIS ✨

int zmq_msg_set (zmq_msg_t *message, int property, int value);

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the vibe. zmq_msg_set() goes and sets the property you named in the property argument to whatever you passed in the value argument, and it does that for the 0MQ message fragment that message is pointing at. simple. chef's kiss. πŸ’…

but bestie… lowkey hear me out: right now, at this very moment, zmq_msg_set() does not support any property names. zero. none. not a single one. it's giving empty menu at a restaurant that's still open 🫠 so like… yeah. the function exists, the vibes exist, the properties do not. 😭

🌸 RETURN VALUE 🌸

if it works, it returns zero. iconique. ✨

if it does not work? it returns -1 and sets errno to one of the values listed below, no cap. 😀


⭐ ERRORS ⭐

  • EINVAL β€” the property you asked for is unknown. like, the property property is unknown. that's the whole tea πŸ“ (and given the description up there… yeah, this is basically the only plot twist available rn πŸ’€)

πŸŽ€ SEE ALSO πŸŽ€

go read those, they're the supporting cast and they ate πŸ”₯


πŸ’œ AUTHORS πŸ’œ

this page was written by the 0MQ community 🫢 if you wanna make a change (and honestly, main character energy, you should), go read the 0MQ Contribution Policy at http://www.zeromq.org/docs:contributing πŸ’–


and that's a wrap, bestie 🌈 this was 0MQ 4.3.5, dated 10/09/2023, and yes the whole thing is ZMQ_MSG_SET(3) iykyk πŸ‘‘βœ¨

πŸ“¦ where this page comes from