TT_MESSAGE_ARG_BVAL(3)

💅 tt_message_arg_bval

Library call page, bestie — that's the manual-name energy right there. This one is all about grabbing the byte-array value of a message argument. No cap.

---

🌸 NAME 🌸

tt_message_arg_bval — retrieve the byte-array value of a message argument. Periodt.

✨ SYNOPSIS ✨

#include &<Tt/tt_c.h>
Tt_status tt_message_arg_bval(
Tt_message m,
int n,
unsigned char **value,
int *len);

🦋 DESCRIPTION 🦋

Okay so tt_message_arg_bval retrieves the byte-array value of the nth message argument. Main character function behavior, truly.

• m — the opaque handle for the message involved in this operation.
• n — the number of the argument to be retrieved. The first argument is numbered zero, so yes, we're doing zero-based indexing, bestie.
• value — the address of a character pointer to which the ToolTalk service is to point a string that contains the contents of the argument.
• len — the address of an integer to which the ToolTalk service is to set the length of the value in bytes.

💖 RETURN VALUE 💖

Upon successful completion, tt_message_arg_bval returns the status of the operation as one of the following Tt_status values:

• TT_OK — The operation completed successfully. Slay.
• TT_ERR_NOMP — The ttsession(1) process is not running and the ToolTalk service cannot restart it.
• TT_ERR_NUM — The integer value passed was invalid (out of range).
• TT_ERR_POINTER — The pointer passed does not point to an object of the correct type for this operation.

Fr fr, those are the statuses — don't sleep on TT_ERR_NOMP, it's giving "no session, no service, no vibes."

🔥 SEE ALSO 🔥

• Tt/tt_c.h - Tttt_c(5). Go read those, iykyk.

---

Cute sign-off time: the footer just repeats tt_message_arg_bval(library call) again, with no separate source/version or date line on this page — so that's the whole library-call moment. 💅✨