buffer_getline(3)

✨ buffer_getline(3) ✨

okay bestie, pull up a chair because we're talking about buffer_getline, a lil function from the Library Functions Manual (section 3, library functions, iykyk 💅). she reads a line from a buffer. that's it. that's the girl. and honestly? iconic. 🎀

---

🌸 NAME 🌸

buffer_getline — read line from buffer 📖✨

---

🦋 SYNTAX 🦋

#include <libowfat/buffer.h>

ssize_t buffer_getline(buffer* b,char* x,size_t len);

like, that's the whole vibe check right there 🫶

---

💖 DESCRIPTION 💖

okay so here's the tea ☕ — buffer_getline copies data from b into x[0], x[1], ..., x[len-1], and it keeps going until either:

• len bytes have been copied, or
• a new-line character ('\n') shows up 👀

and bestie, that new-line character? it gets copied too. it's included. it's part of the group. no cap. 🎉

🚨 not me about to tell you the most important part 🚨 — the line is not 0-terminated! and that's on purpose, fr fr. it's so that reading lines with 0-bytes in them is actually possible through this interface. the 0-bytes get to exist. we love that for them. 🌈

---

👑 RETURN VALUE 👑

• Number of bytes read — and heads up, that count does not include the '\n' ✨
• -1 on error — and yeah, it sets errno when that happens 😭

---

🔥 SEE ALSO 🔥

go read these next, bestie, they're all in the family:

• buffer_init(3)
• buffer_feed(3)
• buffer_peek(3)
• buffer_seek(3)
• buffer(3)

---

and that's the whole page, babes — straight outta the Library Functions Manual, filed under buffer_getline(3) (same name top and bottom, we love consistency 💅). no version or date on this one, just pure unfiltered libowfat energy. stay hydrated, read your buffers, and remember: the '\n' counts as read but not as read-read. periodt. 🫶✨