al_get_fs_entry_size(3alleg5)
π al_get_fs_entry_size β Allegro 5 API π
okay bestie, so this one lives in the allegro5 manual (that's the Allegro 5 reference, the whole girlboss library situation) and it's genuinely so simple you're gonna scream. it's giving "one job, does the one job." periodt.
β¨ NAME β¨
al_get_fs_entry_size β Allegro 5 API
like. the name literally tells you everything. get. fs. entry. size. no cap.
πΈ SYNOPSIS πΈ
#include <allegro5/allegro.h>
off_t al_get_fs_entry_size(ALLEGRO_FS_ENTRY *e)
okay so you gotta pull in allegro5/allegro.h first, obviously, and then you call it with one single ALLEGRO_FS_ENTRY * pointer named e and it hands you back an off_t. that's it. that's the whole vibe. π¦
π DESCRIPTION π
Returns the size, in bytes, of the given entry.
that's the tea. you pass it your entry, it tells you how many bytes that thing is. big fan. π
β οΈ but listen β it may not return anything sensible for a directory entry. like, a directory is a directory, bestie, not a file with a cute little byte count. so if you point this at a folder, don't come crying to me when the number is weird. it's not broken, that's just how it is. the entry is giving chaos and you were warned. π
π SEE ALSO π
al_update_fs_entry(3alleg5)β go refresh that entry first, queen, so your size is actually up to date π«Ά
k bye ily, go read some file sizes π
this was brought to you by the Allegro reference manual, al_get_fs_entry_size(3alleg5), no date bestie it just says the manual and the page and honestly? iconic of it. β¨π
π¦ 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