TT_MESSAGE_ARGS_COUNT(3)

πŸ“¦
version 2.5.3 Β· 2 versions
, in nixos 26.05

πŸŽ€ tt_message_args_count πŸŽ€

okay bestie, you've landed on the tt_message_args_count(library call) page β€” yes, that's the manual name, and no, we're not copying the header line like a robot. This function is lowkey tiny but highkey useful: it tells you how many arguments are sitting in a message. Let's go. πŸ’…

πŸ’– NAME πŸ’–

tt_message_args_count β€” return the number of arguments in the message.

✨ SYNOPSIS ✨

#include &<Tt/tt_c.h>
int tt_message_args_count(
Tt_message m);

🌸 DESCRIPTION 🌸

The tt_message_args_count function returns the number of arguments in the message. That's it, that's the whole job β€” no cap. 🫢

The m argument is the opaque handle for the message involved in this operation. So like, you don't peek inside it, you just pass it in and let the function do its main character thing. ✨

πŸ’… RETURN VALUE πŸ’…

Upon successful completion, the tt_message_args_count function returns the total number of arguments in the message. The application can use tt_int_error(3) to extract one of the following Tt_status values from the returned integer:

  • 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_POINTER β€” The pointer passed does not point to an object of the correct type for this operation. πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘


and that's the whole page, bestie β€” the footer is just the tt_message_args_count(library call) tag, so no extra source/version/date lore to spill. periodt. πŸ’–βœ¨

πŸ“¦ where this page comes from