al_identify_bitmap(3alleg5)
π NAME π
al_identify_bitmap β it's giving Allegro 5 API, bestie β¨ (and yes, that little (3alleg5) after it is just the manual page's section tag, iykyk π)
β¨ SYNOPSIS β¨
#include <allegro5/allegro.h>
char const *al_identify_bitmap(char const *filename)
π¦ DESCRIPTION π¦
okay so al_identify_bitmap is literally the exact same energy as al_identify_bitmap_f(3alleg5) β same behaviour, no cap β except you hand it the filename of the file you wanna type-detect, not a file handle. that's the whole plot twist π
and here's the iconic part: the extension on the filename you pass in? not taken into account. at all. nope. it does not care what you named the thing. picture.png? picture.wav? picture.definitely_not_a_bitmap? doesn't matter, bestie π«Ά it's looking at the file contents and only the file contents. content over branding, main character behaviour fr fr π
β SINCE β
5.1.12 β she's been here since 5.1.12 and she's been slaying ever since π
β¨
πΈ SEE ALSO πΈ
ngl bestie, if you got here from the wrong extension, that's the whole point π the contents are the vibe check π
anyway that's the page!! it's from the Allegro reference manual (that's the source, right there in the footer) and it's the al_identify_bitmap(3alleg5) page, mwah π go identify some bitmaps, you've got this, periodt ππ¦β¨
π¦ where this page comes from
- debian trixie: allegro5-doc 2:5.2.10.1+dfsg-1 Β· Zlib
- ubuntu questing: allegro5-doc 2:5.2.10.1+dfsg-1build1
- ubuntu resolute: allegro5-doc 2:5.2.11.3+dfsg-1 Β· Zlib
- ubuntu stonking: allegro5-doc 2:5.2.11.3+dfsg-1 Β· Zlib
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms