TT_MALLOC(3)

💅 tt_malloc — library call, bestie

okay so this is the tt_malloc page from the library call section, and it's literally one function, so let's get into it 🫶

---

✨ NAME ✨

tt_malloc — allocate storage on the ToolTalk API allocation stack

like, it grabs you some bytes, but make it ~ToolTalk~ 💖

---

🎀 SYNOPSIS 🎀

#include <Tt/tt_c.h>
caddr_t tt_malloc(
size_t s);

yes bestie, that's the whole thing. one include, one call, one size_t. clean. iconic. periodt ✨

---

🌸 DESCRIPTION 🌸

so the tt_malloc function allocates storage on the ToolTalk API allocation stack. that's the vibe. that's what it does. no cap 🧚

the s argument is the amount of storage to be allocated, in bytes. that's it — just tell it how many bytes you need and it handles the rest on that allocation stack 💜

---

🦋 RETURN VALUE 🦋

upon successful completion, the tt_malloc function returns the address of the storage in the ToolTalk API allocation stack that is to be allocated 💅

but — and this is the part where you pay attention — if NULL is returned, no storage is available. like, none. zero. not a single byte 😭 so please check it, k? i'm begging 🙈

---

🌈 APPLICATION USAGE 🌈

okay so this function is the whole reason your application-provided callback routines get to take advantage of the allocation stack 👑

for example — and this is fr fr the example — a query filter function can allocate storage to accumulate a result. so like, your filter callback is out here collecting results and it needs somewhere to put them, and tt_malloc is right there for it 🍓

it's giving main character energy for callbacks, honestly 💀

---

⭐ SEE ALSO ⭐

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

(you're gonna want tt_free(3), bestie — what goes on the allocation stack does not stay on the allocation stack forever 😌)

---

little reminder: this page doesn't tell you what to do with the pointer after you're done — that's what tt_free(3) is for. go read it, iykyk 💖

---

okay that's the whole page! 🌟 it's the tt_malloc(library call) page, and the footer had zero extra lore — no version stamp, no date, just tt_malloc(library call) again, so like... the page said its own name twice and dipped 💀 slay, honestly. byeee 🎀💜