TT_PATTERN_SENDER_PTYPE_ADD(3)

🦋 tt_pattern_sender_ptype_add(3) — library call vibes 🦋

Okay so bestie, this is the manual page for tt_pattern_sender_ptype_add(3), and yes it's a library call page. It's literally the function that adds a value to the sending process's ptype field for a pattern. No cap. 💅

🌸 NAME 🌸

tt_pattern_sender_ptype_add — add a value to the sending process's ptype field for a pattern

🎀 SYNOPSIS 🎀

#include &<Tt/tt_c.h>
Tt_status tt_pattern_sender_ptype_add(
Tt_pattern p,
const char *ptid);

💖 DESCRIPTION 💖

The tt_pattern_sender_ptype_add function adds a value to the sending process's ptype field for the specified pattern. slay.

The p argument is a unique handle for a message pattern. That handle is returned after tt_pattern_create(3) is called. The ptid argument is the character string that uniquely identifies the type of process in which the application is interested. iykyk. 🫶

🔥 RETURN VALUE 🔥

Upon successful completion, the tt_pattern_sender_ptype_add function returns the status of the operation as one of the following Tt_status values:

• TT_OK — The operation completed successfully. periodt.
• TT_ERR_NOMP — The ttsession(1) process is not running and the ToolTalk service cannot restart it. oop — no session, no service restart.
• TT_ERR_POINTER — The pointer passed does not point to an object of the correct type for this operation. vibe check failed on the pointer.

🌈 SEE ALSO 🌈

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

---

Signing off from this library call page for tt_pattern_sender_ptype_add(3) — the original footer just repeated the library call title, and there was no extra date or version listed, so that's the whole source/version/date tea. Bye bestie! 💜🎀