TT_OTYPE_DERIVED(3)

💅 tt_otype_derived 💅

okay so bestie, this is the library call manual page for tt_otype_derived — and yes, it's giving very specific Unix gremlin energy, but we love that for us 🫶.

---

🌸 NAME 🌸

tt_otype_derived — return the ith otype derived from the given otype. no cap, that's literally the whole job 💖

---

✨ SYNOPSIS ✨

#include &<Tt/tt_c.h>
char *tt_otype_derived(
const char *otype,
int i);

---

🦋 DESCRIPTION 🦋

so the tt_otype_derived function returns the ith otype derived from the given otype. iconic behavior, honestly ✨

the otype argument is the object type involved in this operation. and the i argument is the zero-based index into the otypes derived from the given otype — zero-based, bestie, so index 0 is the first one, not index 1. iykyk 💅

---

🔥 RETURN VALUE 🔥

upon successful completion, the tt_otype_derived function returns the name of the ith otype derived from the given otype. slay 🎀

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. periodt 💖
• TT_ERR_NOMP — the ttsession(1) process is not running and the ToolTalk service cannot restart it. 😭
• TT_ERR_OTYPE — the specified object type is not the name of an installed object type. not the vibe 💀

---

🌈 APPLICATION USAGE 🌈

the application should use tt_free(3) to free any data stored in the address returned by the ToolTalk API. yes bestie, free it — don't just leave it sitting there like an unread group chat 🫶

---

👑 SEE ALSO 👑

• Tt/tt_c.h - Tttt_c(5)
• tt_otype_is_derived(3)
• tt_otype_base(3)
• tt_otype_deriveds_count(3)
• tt_spec_type(3)
• tt_message_otype(3)
• tt_ptr_error(3)
• tt_free(3)

---

source/version + date tea 🍓: the footer on this page is just tt_otype_derived(library call) — no separate version or date line is listed. mwah 💋