al_assert(3alleg4)

💖 al_assert — bestie edition ✨

okay so this is al_assert from the Allegro manual, and it's literally the "something is WRONG and I'm saying it OUT LOUD" function. part of the Allegro game programming library, if that wasn't obvious. 🎀

🌸 NAME 🌸

al_assert — asserts at the specified file and line number. Allegro game programming library. she tells you exactly where things went sideways, no cap. 💅

🦋 SYNOPSIS 🦋

#include <allegro.h>

void al_assert(const char *file, int line);

✨ DESCRIPTION ✨

okay so what she does: she raises an assert for an error at the file and line number you hand her. so you point at a spot in your code and she's like "yeah, this one, right here, it's giving broken." 😭

the file parameter is always given in ASCII format. always always. don't get cute with it. 🙈

by default, she calls the system driver's assert handler. iconic delegation honestly. 👑

but — and this is the plot twist — if there is none, the error gets sent to stderr and the program will abort. like, full stop, lights out, bye. 💀

that's a real abort, bestie. the program is not continuing. respect that.

HOWEVER. if the environment variable ALLEGRO_ASSERT is set, this function writes a message into the file specified by that environment variable, and program execution will continue. different vibe entirely. she logs it and moves on, unbothered. 🌈

and if none of these behaviours is what you want? you can override them with a custom assert handler. your code, your rules, periodt. 💜

pro tip (well, it's in the manual so it's a real tip): you will usually want to use the ASSERT() macro instead of calling this function directly. fr fr. she's the machinery, not the steering wheel.

🎀 SEE ALSO 🎀

• ASSERT(3alleg4)
• al_trace(3alleg4)
• register_assert_handler(3alleg4)

okay that's the whole page, you ate it, go assert something responsibly. this was Allegro, version 4.4.3, coming at you from the manual, and your girl al_assert(3alleg4) is signing off. mwah 💋✨🫶