al_fungetc(3)

🎀 NAME 🎀

al_fungetc — Allegro 5 API, coming at you from the Library Functions Manual bestie 💖 (yes, we are absolutely in al_fungetc(3) territory).

✨ SYNOPSIS ✨

#include <allegro5/allegro.h>

int al_fungetc(ALLEGRO_FILE *f, int c)

💅 DESCRIPTION 💅

Okay so al_fungetc is the “oops, put that byte back” girlie 💫. It ungets a single byte from a file — like you read it and now you’re gently yeeting it back for later reads.

Pushed-back bytes are not written to the file, bestie. They’re only made available for subsequent reads, and they come back in reverse order 🌀. That detail is doing main character work, so don’t forget it.

How many pushbacks you get depends on the backend. The standard I/O backend only guarantees a single pushback; the real behavior depends on the libc implementation. So don’t be out here stacking pushbacks like limited-edition Stanley cups unless you know your backend can handle it 🫶.

For backends that follow the standard behavior, the pushback buffer will be cleared after any seeking or writing. Also, calls to al_fseek(3) and al_ftell(3) are relative to the number of pushbacks. And if a pushback causes the position to become negative?

🚨 Warning bestie: the behavior of al_fseek(3) and al_ftell(3) is undefined in that case. Not iconic. Do not collect $200. 💀

👀 SEE ALSO 👀

• al_fgetc(3)
• al_get_errno(3)

---

mwah 💋 — signed off by the Allegro reference manual, al_fungetc(3) edition 🎀 source/version and all. The footer didn’t print a date, so I’m not inventing one, bestie 🌸