al_fungetc(3alleg5)

💖 al_fungetc 💖

okay bestie, so this is a page from the Allegro 5 manual — the al_fungetc one, specifically. sit down, grab a strawberry, and let's get into it 🍓

---

✨ NAME ✨

al_fungetc — Allegro 5 API 👑

---

🌸 SYNOPSIS 🌸

#include <allegro5/allegro.h>

int al_fungetc(ALLEGRO_FILE *f, int c)

---

🦋 DESCRIPTION 🦋

so basically it ungets a single byte from a file. like, you take a byte that was already read and you shove it back in there. and the pushed-back bytes? they are NOT written to the file, no ma'am. they just hang around, made available for the reads that come after — and in reverse order, because of course they do 💅

the number of pushbacks you get depends on the backend, fr fr. the standard I/O backend only guarantees you a single pushback — and honestly even that depends on the libc implementation. so don't get greedy 🙈

for backends that follow the standard behavior: the pushback buffer gets cleared after any seeking or writing. also, calls to al_fseek(3alleg5) and al_ftell(3alleg5) are relative to the number of pushbacks. and if a pushback makes the position go negative?? the behavior of al_fseek(3alleg5) and al_ftell(3alleg5) is undefined. not undefined in a cute mysterious way, undefined in a "we literally cannot tell you what happens" way 💀

⚠️ heads up bestie: undefined behavior is not a vibe. if you're pushing back past the start of the file, you're on your own. proceed with caution 🫶

---

🌈 SEE ALSO 🌈

• al_fgetc(3alleg5)
• al_get_errno(3alleg5)

---

and that's the whole page, bestie 💜 it's from the Allegro reference manual, and the footer was just doing its little al_fungetc(3alleg5) thing again — iconic of it honestly. mwah, go push some bytes back 🎀✨