MM_LOG_FATAL(3)

💅 MM_LOG_FATAL(3) — mmlib library manual 🎀

okay bestie, gather round, because this is the log-level page and it's lowkey iconic. we're in the mmlib library manual and these five functions are literally your group chat of severity levels. let's get into it ✨

---

✨ NAME ✨

mm_log_fatal, mm_log_error, mm_log_warn, mm_log_info, mm_log_debug — add a formatted message to the log file 🫶

that's it, that's the job. five besties, five vibes, one log file. no cap.

---

🌸 SYNOPSIS 🌸

so first, you gotta pull in the header like it's the aux cord:

#include <mmlog.h>

then, the five icons themselves, all serving the exact same signature energy:

void mm_log_fatal(msg, ...);
void mm_log_error(msg, ...);
void mm_log_warn(msg, ...);
void mm_log_info(msg, ...);
void mm_log_debug(msg, ...);

and don't forget to link her up, or she will simply not show up to the party:

Link with -lmmlib

---

🦋 DESCRIPTION 🦋

okay so here's the tea 🍓 — those macros write a log entry (they do it by way of mm_log(3), she's the real one doing the work) and they use the level that matches whatever the macro name says. fatal is fatal, warn is warn, you get it, you're smart, i believe in you 💖

and here's the lil glow-up: if the preprocessor definition MM_LOG_MAXLEVEL is smaller than the level that corresponds to the macro, then that macro is simply not expanded in the code. poof. gone. it doesn't exist in your binary. the compiler doesn't even look at it. it's giving ghosted 👻

now, the module name that shows up inside the location string? that's set by MM_LOG_MODULE_NAME. but if you didn't set it when you included mmlog.h, it auto-initializes itself to the value of PACKAGE_NAME. cute, right? it just knows. ✨

and if MM_LOG_VERBOSE_LOCATION is defined, then the filename and the line number get prepended to that location string. so now your logs are like "yes i know exactly which line did this" and honestly? main character energy 👑

---

💜 RETURN VALUE 💜

None.

nothing. nada. zero. void. it's a void function, bestie, she returns nothing and she's at peace with that 🧘‍♀️

---

🔥 THREAD SAFETY 🔥

mm_log() is thread-safe. 🫶

not the macros specifically, but the mm_log(3) underneath them — that's the one holding it down. so go ahead and log from all your threads, she can handle it 💅

---

🎀 EXAMPLE 🎀

bestie... there is no example. the page is just blank here. not me getting all excited for a demo and there's literally nothing 😭 consider this section a vibe check that we... did not pass. no example for us today 🙈

---

and that's the whole page, babe! this lil masterpiece comes to you from the mmlib library manual, dated 2012, and it's filed under MM_LOG_FATAL(3). slay, mmlib, honestly 👑💖✨