al_rebase_path(3)
π al_rebase_path π
okay bestie, this is al_rebase_path(3) from the Library Functions Manual β and yes, it's giving Allegro 5 API energy. π
β¨ NAME β¨
al_rebase_path β Allegro 5 API
πΈ SYNOPSIS πΈ
#include <allegro5/allegro.h>
bool al_rebase_path(const ALLEGRO_PATH *head, ALLEGRO_PATH *tail)
π DESCRIPTION π
okay so picture this: you're concatenating two path structures, and the second path structure is the one getting modified. That's the whole vibe. π«Ά
If tail is an absolute path, this function does absolutely nothing β like, it's not even gonna touch it. Otherwise, the drive and path components in head are inserted at the start of tail. slay.
For example, if head is β/anchor/β and tail is βdata/file.extβ, then after the call tail becomes β/anchor/data/file.extβ. literally iconic behavior. β¨
π¦ SEE ALSO π¦
source/version: Allegro reference manual; date: the footer doesn't list one, bestie β no date to report, but the page is still al_rebase_path(3) and it ate. periodt. πππ«Ά
π¦ 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