al_get_fs_entry_name(3)
π al_get_fs_entry_name(3) β the Allegro 5 API girlies' guide
okay so bestie, you're in the Library Functions Manual section, and this little icon is from the Allegro 5 API β let's get into it β¨
πΈ NAME
al_get_fs_entry_name β literally the Allegro 5 API, that's the whole vibe π
β¨ SYNOPSIS
#include <allegro5/allegro.h>
const char *al_get_fs_entry_name(ALLEGRO_FS_ENTRY *e)
π¦ DESCRIPTION
So this one returns the entry's filename path, periodt. π«
But here's the tea, and it's important tea: the filesystem encoding may not be known, and the conversion to UTF-8 could β in very rare cases β cause this to return an invalid path. π So it is always safest to access the file over its ALLEGRO_FS_ENTRY(3) and not the path. Like, the entry is the main character here, the path is just... a vibe. π«Ά
On success it returns a read only string which you must not modify or destroy. π«βοΈ Do not touch, do not free, do not redecorate. Returns NULL on failure. π
Note: prior to 5.1.5 it was written: "... the path will not be an absolute path if the entry wasn't created from an absolute path". This is no longer true. πβ¨ (history lesson over, slay)
π SEE ALSO
ngl there's no SEE ALSO section on this page, but ALLEGRO_FS_ENTRY(3) is the icon you actually want to be hanging out with π
and that's the whole page bestie! π this cutie came to you straight from the Allegro reference manual, repping al_get_fs_entry_name(3) β go forth and access your files through the entry, not the path, iykyk π
π₯
π¦ 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