TT_DEFAULT_PTYPE(3)

💖 tt_default_ptype — library call 💖

okay bestie, welcome to the tt_default_ptype page from the library call manual — this one is short, cute, and very “tell me what the default ptype is right now.” 🎀✨

---

🌸 NAME 🌸

tt_default_ptype — retrieve the current default ptype. slay. 💅

---

✨ SYNOPSIS ✨

#include &<Tt/tt_c.h>
char *tt_default_ptype(void)

---

🦋 DESCRIPTION 🦋

The tt_default_ptype function retrieves the current default ptype. lowkey straightforward, highkey useful. 🫶

When the application declares a ptype, the ptype becomes the default. periodt. 🌟

---

🔥 RETURN VALUE 🔥

Upon successful completion, the tt_default_ptype function returns a pointer to a character string that uniquely identifies the current default process type. iconic behavior. 👑

If the pointer is NULL, no default ptype is set. that’s the whole vibe check there. 💀

The application can use tt_ptr_error(3) to extract one of the following Tt_status values from the returned pointer:

• TT_OK — The operation completed successfully. yay! 🎉
• TT_ERR_NOMP — The ttsession(1) process is not running and the ToolTalk service cannot restart it. 😭
• TT_ERR_PROCID — The current default process identifier is out of date or invalid. bestie, that ID is giving expired. 🙈

---

🧚 APPLICATION USAGE 🧚

The application should use tt_free(3) to free any data stored in the address returned by the ToolTalk API. don’t leave that memory just sitting there, babes. 💖

---

🌈 SEE ALSO 🌈

Tt/tt_c.h - Tttt_c(5), tt_ptype_declare(3), tt_ptr_error(3), tt_free(3).

---

Cute footer sign-off: this is the tt_default_ptype(library call) page, and ngl there’s no extra date or version info down in the footer — just that library call label doing its little thing. mwah. 💋✨💅