TT_OTYPE_OSIG_ARG_TYPE(3)

🎀 tt_otype_osig_arg_type — library call, bestie 🎀

🌸 NAME 🌸

Returns the data type of an argument of a notice signature of an otype. Like, that’s literally the whole job. 💅

---

✨ SYNOPSIS ✨

#include &<Tt/tt_c.h>
char *tt_otype_osig_arg_type(
const char *otype,
int sig,
int arg);

---

🦋 DESCRIPTION 🦋

Okay so tt_otype_osig_arg_type returns the data type of the argth argument of the sigth notice signature of the given otype. No cap.

• <italic>otype</italic> is the object type involved in this operation.
• <italic>sig</italic> is the zero-based index into the notice signatures of the specified <italic>otype</italic>.
• <italic>arg</italic> is the zero-based index into the arguments of the specified signature.

Indexes start at zero, bestie — that part is important. 🫶

---

💖 RETURN VALUE 💖

Upon successful completion, tt_otype_osig_arg_type returns the data type of the specified argument. The application can use tt_ptr_error(3) to extract one of the following Tt_status values from the returned pointer:

• TT_OK — The operation completed successfully.
• 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_OTYPE — The specified object type is not the name of an installed object type.

So yeah, vibe check your return pointer with tt_ptr_error(3). 😌✨

---

🫶 APPLICATION USAGE 🫶

The application should use tt_free(3) to free any data stored in the address returned by the ToolTalk API. Free the data, bestie — don’t just leave it floating around like an unread group chat. 💀

---

🌈 SEE ALSO 🌈

• Tt/tt_c.h - Tttt_c(5), tt_otype_osig_arg_mode(3), tt_otype_osig_count(3), tt_otype_osig_args_count(3), tt_otype_osig_op(3), tt_free(3).

---

And that’s the footer, bestie: this is the tt_otype_osig_arg_type library-call page, and the original footer didn’t list a source/version or date, so no extra numbers to spill 💅🫶