NE_BUFFER(3)

📦
version 0.37.1 · 12 versions
, in arch rolling

🌸 NAME 🌸

ne_buffer — string buffer handling. Also hii, this is NE_BUFFER(3) from the neon API reference, and we're about to understand string buffers together, bestie 💖✨

✨ SYNOPSIS ✨

copy this exactness, no cap:

#include <ne_string.h>

typedef struct {
    char *data;
    size_t used;
    size_t length;
} ne_buffer;

🦋 DESCRIPTION 🦋

okay so the ne_buffer type is an expandable memory buffer for holding NUL-terminated strings. slay. The data field points to the beginning of the string, and the length of that string is the used field. The current size of memory allocated is the length field. It is not recommended that the fields of a buffer are manipulated directly, bestie — like, leave them alone. Also important: the data pointer may change when the buffer is modified, so don't get attached to a pointer value, because it can literally move on you 😭.

A buffer is created using ne_buffer_create(3) or ne_buffer_ncreate(3), and destroyed using ne_buffer_destroy(3) or ne_buffer_finish(3). To append data to a buffer, use ne_buffer_append(3), ne_buffer_zappend(3), or ne_buffer_concat(3). those are the appending girlies ✨.

if you modify the string referenced by the data pointer directly — instead of using one of the functions listed above — ne_buffer_altered must be called. that's not optional, iykyk 💅.

Copyright © 2001-2026 Joe Orton. the legal icon, periodt.

okay that's the whole page, bestie 🫶 source/version: neon, date: 03/20/2026, copyright: © 2001-2026 Joe Orton. bye and stay cute 💜🎀

📦 where this page comes from