TT_MESSAGE_SENDER(3)
β¨ NAME β¨
tt_message_sender β from the library call manual: retrieve the sender attribute from a message. π
πΈ SYNOPSIS πΈ
#include &<Tt/tt_c.h>
char *tt_message_sender(
Tt_message m);
π DESCRIPTION π
Okay so tt_message_sender retrieves the sender attribute from the message you point it at. The m argument is the opaque handle for the message involved in this operation. π«Ά
π₯ RETURN VALUE π₯
Upon successful completion, tt_message_sender returns the character value that uniquely identifies the sending process. Iconic. Your app can use tt_ptr_error(3) to extract one of these Tt_status values from the returned pointer:
TT_OKβ the operation completed successfully. slay β¨TT_ERR_NOMPβ thettsession(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. rude, but ok π
π APPLICATION USAGE π
Your app should use tt_free(3) to free any data stored in the address returned by the ToolTalk API. seriously bestie, free it fr fr π§
π SEE ALSO π
Tt/tt_c.h-Tttt_c(5), tt_ptr_error(3), tt_free(3).
ok bye bestie π β that's the whole tt_message_sender page from the library call manual. No source version or date is listed on the page, so no extra deets to spill. π
π¦ where this page comes from
- nixos 26.05: cde 2.5.3
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms