al_join_paths(3)
β¨ al_join_paths(3) β¨
okay so bestie, welcome to the Allegro 5 API page for al_join_paths π
this one's a path-gluing icon and she's about to make your two path structs hold hands π«Ά
πΈ SYNOPSIS πΈ
#include <allegro5/allegro.h>
bool al_join_paths(ALLEGRO_PATH *path, const ALLEGRO_PATH *tail)
π DESCRIPTION π
So what she does is concatenate two path structures β¨ and the first path structure is the one that gets modified β she's the main character here, tail is just visiting πββοΈ
If tail is an absolute path, this function literally does nothing. like, nothing nothing. no cap, she just sits there π
If tail is a relative path, then all of its directory components get appended to path. and bestie, listen β tail's filename will also overwrite path's filename, even if it is just the empty string π so yes, empty string counts, she will absolutely clobber it fr fr
Tail's drive is ignored. ππ¨ don't ask, it's just not invited to the party
She returns true if tail was a relative path and so got concatenated onto path, otherwise she returns false π
lowkey important vibe check: absolutetail= no changes at all, so don't be surprised when yourpathcomes back looking identical π
π¦ SEE ALSO π¦
al_rebase_path(3)β her sibling, go say hi π
β¨ that's the whole page, slay β¨ this was the Allegro reference manual entry for al_join_paths(3), brought to you by the Allegro reference manual, 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