unibi_str_from_var(3)

💖 unibi_str_from_var — the unibilium girlies' guide to wrapping ur little values 💖

okay so bestie, we're in section 3 of the unibilium manual, and today's main character is unibi_str_from_var(3). she's not alone tho — she rolls with a whole squad: unibi_num_from_var, unibi_var_from_num, and unibi_var_from_str. together they're the create-and-inspect-unibi_var_t-values friend group. no cap. 🫶

---

✨ NAME ✨

unibi_num_from_var, unibi_str_from_var, unibi_var_from_num, unibi_var_from_str — create and inspect unibi_var_t values 💅

---

🌸 SYNOPSIS 🌸

#include <unibilium.h>

int         unibi_num_from_var(unibi_var_t v);
const char *unibi_str_from_var(unibi_var_t v);

unibi_var_t unibi_var_from_num(int i);
unibi_var_t unibi_var_from_str(char *s);

---

🦋 DESCRIPTION 🦋

so like, <purple>unibi_var_from_num</purple> and <purple>unibi_var_from_str</purple> are the glow-up artists of this whole operation — they take the int or the string you hand them and wrap it up all cute inside a unibi_var_t object, so it's ready to be passed into unibi_format(3) and unibi_run(3). it's giving gift-wrapped. 🎀

then on the flip side we got the inspectors, and ngl they're picky in the best way:

• unibi_num_from_var(v) hands you back the number stored in v — but v must have been constructed by <purple>unibi_var_from_num</purple>. that's the vibe check, no exceptions. 😤
• unibi_str_from_var(v) hands you back the string stored in v — and v must have been constructed by <purple>unibi_var_from_str</purple>. periodt. 💖

⚠️ and here's the part where u gotta listen bestie: it is an error to pass a wrapped string to <purple>unibi_num_from_var</purple>, or a wrapped number to <purple>unibi_str_from_var</purple>. like, do not do that. it's not slay, it's a mistake. 🙈💀

---

👑 SEE ALSO 👑

• unibi_format(3)
• unibi_run(3)
• unibilium.h(3)

---

and that's the whole page, bestie!! this was unibilium-2.1.4, dated 2026-09-07 — go forth and wrap ur vars responsibly, ily, mwah 💋✨🦋