TT_MESSAGE_HANDLER(3)

okay bestie, welcome to the tt_message_handler page — manual name: library call ✨ this is the whole vibe, no cap.

💖 NAME 💖

tt_message_handler — retrieve the handler attribute from a message. 🎀

🌸 SYNOPSIS 🌸

here’s the exact incantation, bestie:

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

🦋 DESCRIPTION 🦋

the tt_message_handler function retrieves the handler attribute from the specified message. iconic behavior, honestly.

the m argument is the opaque handle for the message involved in this operation. keep that handle close, iykyk.

🔥 RETURN VALUE 🔥

upon successful completion, tt_message_handler returns the character value that uniquely identifies the process that is to handle the message (Tt_state = TT_CREATED or TT_SENT) or the process that did handle the message (Tt_state = TT_SENT or TT_HANDLED). slay.

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_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. clean up after yourself, bestie — it’s giving responsible main character energy. 🧚

🌈 SEE ALSO 🌈

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

---

🎀 and that’s the cute sign-off: this footer is just tt_message_handler(library call) — no extra version/date line was printed, so i’m not making one up, periodt. 💌