buffer_getc(3)

πŸ“¦
version 0.34 Β· 2 versions
  • 0.34 Β· alpine 3.24, debian bookworm, debian trixie, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 0.30 Β· fedora 43, fedora 44, ubuntu jammy
, in alpine 3.24, debian bookworm, debian trixie, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

✨ buffer_getc(3) ✨

okay so bestie, welcome to buffer_getc from the Library Functions Manual, section 3 β€” it's the libowfat girlies' lil one-char-at-a-time moment and honestly? she's serving simplicity. πŸŽ€


🌸 NAME 🌸

buffer_getc β€” read one char from buffer πŸ’…

like, one (1) single char. that's the whole job. no cap. πŸ¦‹


🫢 SYNTAX 🫢

#include <libowfat/buffer.h>

int buffer_getc(buffer* b,char* x);

yeah she takes a buffer* and a char* and hands you back an int. iconic behaviour, no notes. ⭐


πŸ’– DESCRIPTION πŸ’–

buffer_getc(b,x) is similar to buffer_get(b,x,1).

that's it, that's the lore 😭 β€” it's literally just the "gimme exactly one char" shortcut, i.e. the buffer_get girlies with the length hardwired to 1. if you already know buffer_get, you already know her. iykyk. πŸ’œ


πŸ‘‘ SEE ALSO πŸ‘‘

go read the whole friend group, they're all connected besties 🧚✨


and that's the page!! the tag on this one is just buffer_getc(3) β€” no source, no version, no date dropped anywhere on it, so that's all the sign-off we get, and we're obsessed with the minimalism fr fr πŸ’€πŸ«Ά