iv_fatal(3)

✨ iv_fatal — ivykis programmer's manual ✨

okay bestie, pull up a chair, because we're talking about iv_fatal(3) and iv_set_fatal_msg_handler — the ivykis fatal error condition handling duo 💀✨ iykyk.

🎀 NAME 🎀

iv_fatal, iv_set_fatal_msg_handler — ivykis fatal error condition handling

🦋 SYNOPSIS 🦋

#include <iv.h>

void iv_fatal(const char *fmt, ...);
void iv_set_fatal_msg_handler(void (*handler)(const char *msg));

💖 DESCRIPTION 💖

so. iv_fatal aborts the running program 😭 — like, the whole thing, gone — but it might emit an error message first. That fmt parameter? It's a printf(3)-style format string, and it's literally the message that gets logged. Very demure, very mindful of your logs.

If no handler is set (which is the default, the factory setting, the no-makeup-makeup look), then the formatted message gets sent to syslog, with critical severity 🔥. Otherwise, the handler you set with iv_set_fatal_msg_handler is used instead. Your handler, your rules 💅.

Also important: iv_fatal is also used internally by ivykis, whenever a fatal situation is detected. So she's not just a public-facing icon, she's working behind the scenes too. main character energy fr fr 👑

Now, iv_set_fatal_msg_handler — you use this to set an alternative function to call from iv_fatal, as opposed to syslog. And the argument you pass should be a function that does not return, and takes a single string as its argument — that string being the formatted error message. No cap: if your handler returns, you've broken the vibe. It's giving "must not return" periodt.

⚠️ warning bestie: the handler you set has to not return, and it takes exactly one string argument — the formatted error message. Don't get cute with it.

🌸 SEE ALSO 🌸

• ivykis(3)
• iv_examples(3)

and that's the whole page, bestie 🫶 go forth and handle your fatal errors with grace 💖🧚✨

ivykis · 2012-06-18 · iv_fatal(3) — mwah, iconic, no notes 💅🎀