TT_PTYPE_OPNUM_CALLBACK_ADD(3)

🌸 NAME 🌸

tt_ptype_opnum_callback_add — return a callback if two opnums are equal. This is a library call, bestie, and we are about to understand it fr fr 💅✨

✨ SYNOPSIS ✨

#include &<Tt/tt_c.h>
Tt_status tt_ptype_opnum_callback_add(
const char *ptid,
int opnum,
Tt_message_callback f);

🦋 DESCRIPTION 🦋

Okay so tt_ptype_opnum_callback_add returns a callback if the specified opnums are equal. The callback is defined in Tt/tt_c.h - Tttt_c(5). Iconic.

When a message is delivered because it matched a pattern derived from a signature in the named ptype with an opnum equal to the specified one, the given callback is run in the usual ToolTalk way. Periodt.

• ptid — the identifier of the ptype involved in this operation.
• opnum — the opnum of the specified ptype.
• f — the message callback to be run.

👑 RETURN VALUE 👑

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

• TT_OK — The operation completed successfully. Slay.
• TT_ERR_PTYPE — The specified process type is not the name of an installed process type.
• TT_ERR_POINTER — The pointer passed does not point to an object of the correct type for this operation.
• TT_ERR_NOMP — The ttsession(1) process is not running and the ToolTalk service cannot restart it.

🎀 APPLICATION USAGE 🎀

The tt_ptype_opnum_callback_add function will only be called for messages delivered by virtue of matching handler signatures. The callback cannot be called for observer signatures because the observer ptype is not recorded in the incoming message. No cap.

🌈 SEE ALSO 🌈

• Tt/tt_c.h - Tttt_c(5).

---

xoxo bestie 💖 — the footer source/version line is tt_ptype_o...allback_add(library call), and the date on this page is not shown, no cap 😭✨