al_destroy_bitmap(3)
okay so you're on the al_destroy_bitmap(3) page from the Library Functions Manual, and it's giving "cleanup era" for your Allegro 5 bitmaps. let's go bestie π
β¨
π NAME π
al_destroy_bitmap β Allegro 5 API
β¨ SYNOPSIS β¨
#include <allegro5/allegro.h>
void al_destroy_bitmap(ALLEGRO_BITMAP *bitmap)
π DESCRIPTION π
al_destroy_bitmap destroys the given bitmap and frees literally all the resources used by it. like, full bye-bye, resources released, iconic behavior ππ₯
If the bitmap argument is NULL, this function does nothing. not a single thing. it simply does not engage π«Ά
Here's the convenience part: if the calling thread is currently targeting the bitmap, then the bitmap will be untargeted first. The new target bitmap is unspecified. (since: 5.0.10, 5.1.6) β yes, that's the exact little caveat, bestie π¦
β οΈ Otherwise, it is an error to destroy a bitmap while it (or a sub-bitmap) is the target bitmap of any thread. this is not a drill β that's an error, so don't do it ππ
π¦ SEE ALSO π¦
π xoxo, the Allegro reference manual β al_destroy_bitmap(3) signing off, bestie! π
π¦ where this page comes from
- arch rolling: allegro 5.2.11.3-2 Β· Zlib AND BSD-3-Clause AND OFL-1.1 AND LicenseRef-Custom
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms