al_join_paths(3alleg5)
π NAME π
hey bestie, welcome to the al_join_paths(3alleg5) page from the Allegro reference manual! This one is all about al_join_paths β Allegro 5 API, and it's lowkey iconic for path girlypops.
β¨ SYNOPSIS β¨
#include <allegro5/allegro.h>
bool al_join_paths(ALLEGRO_PATH *path, const ALLEGRO_PATH *tail)
π¦ DESCRIPTION π¦
okay so picture two path structs, and we're gonna concatenate them. The first path structure, path, gets modified. She's the main character and she's changing in place, periodt.
If tail is an absolute path, this function does nothing. Like, absolutely nothing, no cap. It just sits there looking pretty.
If tail is a relative path, then all of its directory components get appended to path. Also, tailβs filename will overwrite pathβs filename β even if it is just the empty string. Yes bestie, even "" is out here overwriting things. π
Tailβs drive is ignored. Not invited to the function, not on the guest list, bye. π
It returns true if tail was a relative path and so concatenated to path; otherwise it returns false. So like, a little bool vibe check for you.
π SEE ALSO π
xoxo, signing off from the Allegro reference manual β al_join_paths(3alleg5) β and the footer didn't give me a date, so that's all she wrote ππ
π¦ 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