unibi_int_from_var(3)

💖 unibi_int_from_var — the unibilium glow-up guide 💖

okay bestie, so this is a page from unibilium(3), and it's literally all about wrapping numbers and strings up in little unibi_var_t packages and then peeking back inside them. it's giving ✨ gift wrap and un-wrap ✨ and honestly? we're obsessed.

---

🌸 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);

like, four little functions, all matching, all iconic 💅

---

🦋 DESCRIPTION 🦋

so <rainbow>unibi_var_from_num</rainbow> and <rainbow>unibi_var_from_strare the wrappers, right? they take theintor the string you hand them and tuck it all cozy inside aunibi_var_tobject so it can be used inunibi_format(3)andunibi_run(3)`. it's their whole thing. they're built for it. no cap. 🫶

then we got the inspectors:

• <cyan>unibi_num_from_var(v)</cyan> returns the number stored in v — and listen, v must have been constructed by unibi_var_from_num. that's not optional, that's the vibe check.
• <cyan>unibi_str_from_var(v)</cyan> returns the string stored in v — and v must have been constructed by unibi_var_from_str. same energy, same rule.

🚨 okay but this part is IMPORTANT, bestie. it is an error to pass a wrapped string to unibi_num_from_var or a wrapped number to unibi_str_from_var. do not do it. i'm literally begging. that's the 💀 path and we are NOT walking it. 🙈

---

👑 SEE ALSO 👑

unibilium.h(3)

---

and that's the whole page, fr fr ✨ this was unibilium-2.1.4, dated 2026-09-07, signing off — go wrap something in a unibi_var_t and slay the day 💖💅🌈