TT_MESSAGE_DESTROY(3)

🎀 tt_message_destroy — destroy a message 🎀

okay so bestie, this is the library call page for tt_message_destroy, and it’s giving “clean up this message handle” energy. No cap. 💅

✨ NAME ✨

• tt_message_destroy — destroy a message.

🛠️ SYNOPSIS 🛠️

       #include &<Tt/tt_c.h>
       Tt_status tt_message_destroy(
       Tt_message m);

💖 DESCRIPTION 💖

So the tt_message_destroy function destroys the message. That’s the whole assignment, periodt. 🫶

Destroying a message has no effect on the delivery of a message already sent. That part is literally untouched, bestie. ✨

The m argument is the opaque handle for the message involved in this operation. Opaque handle means you don’t peek inside, you just pass it along. 💅

🔥 RETURN VALUE 🔥

Upon successful completion, tt_message_destroy returns the status of the operation as one of these 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_POINTER — The pointer passed does not point to an object of the correct type for this operation. 🚩

🫶 APPLICATION USAGE 🫶

If the application sent a request and is expecting a reply with return values, the application should destroy the message after it has received the reply. Timing matters, bestie. ⏳

If the application sends a notice, the application can destroy the message immediately after it sends the notice. Different vibe, different cleanup window. 💅

👀 SEE ALSO 👀

Tt/tt_c.h - Tttt_c(5), tt_message_create(3), tt_message_create_super(3).

---

That’s the whole page, bestie 🫶 source/version: tt_message_destroy(library call); date: not present in this footer. 💖