al_ustr_insert_chr(3alleg5)
β¨ al_ustr_insert_chr β Allegro 5 API β¨
okay bestie, sit down, hydrate, and let me tell you about al_ustr_insert_chr from the Allegro 5 API π this is a <3alleg5> manual page and honestly? she's a little icon. π
πΈ SYNOPSIS πΈ
#include <allegro5/allegro.h>
size_t al_ustr_insert_chr(ALLEGRO_USTR *us, int pos, int32_t c)
π¦ DESCRIPTION π¦
So the whole vibe here is: we're slipping one single code point into us, and it starts landing at the byte offset pos. π
posliterally cannot be less than0. Not negotiable, not even a little. π ββοΈ- and if
posis past the end ofus? then the gap between where the string ends and whereposis gets padded withNUL('\0') bytes. yes fr fr, she just fills the empty space with NULs like it's nothing. π
Returns the number of bytes inserted β or 0 on error. π«Ά
π SEE ALSO π
al_ustr_insert(3alleg5)al_ustr_insert_cstr(3alleg5)
and that's the whole page, bestie, you ate it. π no cap. this was the Allegro reference manual, and the header up top was al_ustr_insert_chr(3alleg5) in case you forgot where you were. go forth and insert those code points responsibly, mwah πβ¨π§
π¦ 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