al_join_paths(3)

πŸ“¦
version 5.2.11.3 Β· 3 versions
, in arch rolling

✨ 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: absolute tail = no changes at all, so don't be surprised when your path comes back looking identical πŸ’€

πŸ¦‹ SEE ALSO πŸ¦‹


✨ 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