iv_main(3)

💖 iv_main(3) — the ivykis programmer's manual, but make it cute 💖

okay bestie, sit down, hydrate, and let me tell you about iv_main — straight out of the ivykis programmer's manual. this is the function that literally starts the party for your thread. no cap. 🎀

✨ NAME ✨

iv_main — enter the ivykis main loop. that's it. that's the whole job. she walks in, she runs the loop. main character energy fr fr. 👑

🌸 SYNOPSIS 🌸

#include <iv.h>

void iv_main(void);

no args, no return value, no drama. void in, void out. she's mysterious like that. 💅

🦋 DESCRIPTION 🦋

okay so, iv_main enters the current thread's ivykis main loop. current thread. that's important, bestie — i'll get to why in a sec. 🫶

and what even is the ivykis main loop, you ask? it's this whole situation:

• it checks the status of all the registered file descriptors, timers and tasks, and then
• it either calls the callback functions that correspond to the objects that are active, or
• it just blocks until an event shows up. 🌈

like, it's either doing the thing or waiting very patiently for the thing. both are valid. both are iconic. ✨

and here's the part that makes her different from every other main loop out there: every thread that wants to use ivykis has to call iv_main individually. individually!! each thread!! her own call!! no sharing, no borrowing, no "oh my friend already called it." 🙈

⚠️ and bestie, listen — you can only do this after you've already called iv_init(3) earlier. iv_init first, iv_main second. that's the order. do not skip step one. do not flip them. that's it, that's the rule. 💀

👑 SEE ALSO 👑

• ivykis(3) — the whole vibe, the mothership 🌟
• iv_examples(3) — examples!! if you learn by reading code like me 🍓
• iv_quit(3) — the one you call when you want the loop to, uh, stop 🧚

and that's the page, bestie!! it's from the ivykis crew and it's dated 2010-08-15 — old enough to be vintage, still serving 💜 go forth, call iv_init first, then iv_main, and slay. periodt. 💖✨🎀