al_remove_filename(3)

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

al_remove_filename(3) πŸ—‘οΈβœ¨

okay so this is the al_remove_filename(3) page from the Library Functions Manual, and it’s lowkey a tiny baddie: one function, one job β€” delete a path. Allegro 5 API energy all the way. πŸ’–

✨ NAME ✨

  • al_remove_filename β€” Allegro 5 API, bestie. That’s the whole name section, and yes it ate. πŸ‘‘

🌸 SYNOPSIS 🌸

#include <allegro5/allegro.h>

bool al_remove_filename(const char *path)

πŸ’… DESCRIPTION πŸ’…

Delete the given path from the filesystem, bestie. That path may be a file or an empty directory β€” yes, empty, okay? πŸ‘€

This is literally the same as al_remove_fs_entry(3), except it expects the path as a string. No cap. 🧚

It returns true on success and false on failure. And Allegro’s errno is filled in to indicate the error, so if it flops you can go check why. The way that’s useful? Obsessed. πŸ˜­πŸ’œ

πŸ¦‹ SEE ALSO πŸ¦‹

  • al_remove_fs_entry(3) β€” the sibling function this one is the same as, except for the string-path thing. Go read it, iykyk. 🫢

Source/version: Allegro reference manual. Date: not specified in the original footer, so I’m not making one up, periodt. al_remove_filename(3) out β€” slay and stay safe deleting your paths! πŸ’…βœ¨πŸŽ€

πŸ“¦ 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