TT_MESSAGE_SCOPE(3)

💖 NAME 💖

okay so this is the tt_message_scope page from the library call corner, and it's giving one very specific job: retrieve the scope attribute from a message. That's the whole assignment, bestie. 💅

✨ SYNOPSIS ✨

#include &<Tt/tt_c.h>
Tt_scope tt_message_scope(
Tt_message m);

🦋 DESCRIPTION 🦋

The tt_message_scope function retrieves the scope attribute from the specified message. Literally just scope-retrieval energy. No cap. ✨

The m argument is the opaque handle for the message involved in this operation. Opaque handle, iykyk. 🫶

🎀 RETURN VALUE 🎀

Upon successful completion, the tt_message_scope function returns a value that identifies the set of processes eligible to receive the message. The following values are defined:

• TT_SESSION — all processes joined to the indicated session are eligible.
• TT_FILE — all processes joined to the indicated file are eligible.
• TT_BOTH — all processes joined to either indicated file or the indicated session are eligible.
• TT_FILE_IN_SESSION — all processes joined to both the indicated file and the indicated session are eligible.

The application can use tt_int_error(3) to extract one of the following Tt_status values from the Tt_scope integer return value:

• 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 🌈

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

---

that's the whole tt_message_scope(library call) page from the library-call section, no date/version listed — byeee, mwah 💅💖