vrb_new_opt(3)

πŸ“¦ version 0.5.1, in nixos 26.05

πŸ’– NAME πŸ’–

okay so bestie, this is vrb_new_opt(3) from the VRB Programmer's Manual β€” and it does exactly what it says on the tin: vrb_new_opt β€” create a new virtual ring buffer. iconic. πŸ’…

πŸ¦‹ LIBRARY πŸ¦‹

  • -lvrb β€” the library you link against, bestie. that's the whole section, no cap. 🫢

✨ SYNOPSIS ✨

#include <vrb.h>

vrb_p vrb_new_opt(size_t size, const char *name, int options);

🌸 DESCRIPTION 🌸

okay so vrb_new_opt creates a new instance of a virtual ring buffer. no cap.

A virtual ring buffer is a character FIFO queue with the special property that any sequence of characters in the buffer may be accessed as a single contiguous block of memory, eliminating the need to split any sequence to handle a buffer wraparound. it's giving main character energy: no seams, no drama, just one block. ✨

πŸŽ€ ARGUMENTS πŸŽ€

πŸ“ size_t size

this is the requested minimum buffer size to be allocated. the given value will be rounded up to the nearest or equal whole multiple of the system page size. the virtual ring buffer is implemented by mapping two adjacent blocks of memory to the same memory object. thus, twice as much virtual address space will be used and the specified size must be less than half of the available virtual address space for this process. so yeah, not me ignoring that limit, bestie 😭

πŸ¦‹ const char *name

this specifies an optional temporary name pattern or an actual name of a file to be used as backing store via mmap(2) in a mounted filesystem in which the process has write permission. if the name string ends in "XXXXXX" then mkstemp(3) will be used to make the file unique. otherwise it will be used as is. if the named file already exists or otherwise cannot be opened for write, an error will occur. if NULL is given, swap space will be used as backing store via shmat(2). iykyk. πŸ’œ

⭐ int options

this specifies option flags that may be given to alter the behaviour of the virtual ring buffer. the implemented options are:

  • VRB_NOGUARD β€” do not include guard pages that would protect against buffer overflow errors.
  • VRB_ENVGUARD β€” override VRB_NOGUARD if the environment variable VRBGUARD is defined with a value other than the string "0".

⭐ RETURN VALUE ⭐

πŸ’– vrb_p

on success, a handle (pointer) to the newly created virtual ring buffer is returned. on error, NULL is returned. so if you get NULL, that's your vibe check saying "nope". πŸ’€

πŸ’€ ERRORS πŸ’€

if an error is returned, then errno will have one of the following values:

  • EINVAL β€” a buffer size was requested which is too large for address space allocation arithmetic.
  • ENOMEM β€” out of memory allocating the virtual ring buffer structure.
  • - β€” an errno value set by a failing system call.

πŸ‘‘ SEE ALSO πŸ‘‘

go read these too, bestie β€” this list ate: vrb(3), vrb_capacity(3), vrb_data_len(3), vrb_data_ptr(3), vrb_destroy(3), vrb_get(3), vrb_get_min(3), vrb_give(3), vrb_init(3), vrb_init_opt(3), vrb_is_empty(3), vrb_is_full(3), vrb_is_not_empty(3), vrb_is_not_full(3), vrb_move(3), vrb_new(3), vrb_put(3), vrb_put_all(3), vrb_read(3), vrb_read_min(3), vrb_resize(3), vrb_space_len(3), vrb_space_ptr(3), vrb_take(3), vrb_uninit(3), vrb_write(3), vrb_write_min(3).


sign-off πŸŽ€: this page is from vrb, dated 2002-09-30, and it's the vrb_new_opt(3) manual page. periodt. πŸ’–

πŸ“¦ where this page comes from