TT_MESSAGE_OTYPE(3)

💖 NAME 💖

okay so bestie, this is the tt_message_otype(library call) page, and the whole mission is literally: retrieve the object type attribute from a message. no cap. ✨

---

✨ SYNOPSIS ✨

the signature is giving exactly this, and yes, copy it character-for-character:

#include &<Tt/tt_c.h>
char *tt_message_otype(
Tt_message m);

periodt. 🫶

---

🦋 DESCRIPTION 🦋

tt_message_otype retrieves the object type attribute from the specified message. iconic behavior, honestly.

the m argument is the opaque handle for the message involved in this operation — that’s the main character energy right there. not me being obsessed with an opaque handle, but here we are. iykyk. 💅

---

🌸 RETURN VALUE 🌸

upon successful completion, tt_message_otype returns the type of the object involved in this message. 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. slay. 💖
• TT_ERR_NOMP — the ttsession(1) process is not running and the ToolTalk service cannot restart it. highkey stressful. 💀
• TT_ERR_POINTER — the pointer passed does not point to an object of the correct type for this operation. 🙈

---

🎀 APPLICATION USAGE 🎀

the application should use tt_free(3) to free any data stored in the address returned by the ToolTalk API. literally do not ghost the cleanup step, bestie. 🫶

---

🌈 SEE ALSO 🌈

• Tt/tt_c.h - Tttt_c(5), tt_ptr_error(3), tt_free(3). 👑

---

and that’s the tea, bestie — vibe check: passed 💖 signing off from the tt_message_otype(library call) zone. the footer/source/version mention is tt_message_otype(library call), and this page didn’t give me a date, so I’m not inventing one. periodt. 🎀