al_ustr_remove_chr(3)

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

🌸 NAME 🌸

al_ustr_remove_chr β€” Allegro 5 API, and yes bestie, the manual name is Library Functions Manual, folded in right here where you can see it ✨

✨ SYNOPSIS ✨

#include <allegro5/allegro.h>

bool al_ustr_remove_chr(ALLEGRO_USTR *us, int pos)

πŸ’… DESCRIPTION πŸ’…

okay so al_ustr_remove_chr removes the code point that begins at byte offset pos. It returns true on success β€” slay. πŸ’–

If pos is out of range, or if pos is not the beginning of a valid code point, it returns false and leaves the string unmodified. No sneaky edits, no crumbs, periodt. πŸ’€

Use al_ustr_offset(3) to find the byte offset for a code-points offset. iykyk 🫢

bestie PSA: pos is a byte offset, so if you're thinking in code-point offsets, go get the byte offset with al_ustr_offset(3) first. 🌸

πŸ”₯ SEE ALSO πŸ”₯

al_ustr_remove_range(3) β€” go check it out, it's giving related-function energy πŸ‘‘


okay bye bestie! 🫢 source: Allegro reference manual Β· version: Allegro 5 API Β· date: not listed on this page πŸ’…βœ¨

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