al_identify_bitmap(3alleg5)

πŸ“¦
version 5.2.11.3 Β· 4 versions
, in debian trixie, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– 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