How oomsveta/get-next-line works
This is a small C library that returns one allocated line per call from a file descriptor, using bounded reads and retaining unread bytes between calls. The mandatory implementation keeps one static buffer; the bonus implementation tracks a separate buffer per descriptor. Both grow reusable storage, locate line boundaries, and extract results. The README also documents arbitrary BUFFER_SIZE and binary-data handling. Relationships below follow the sampled implementations and README; no unsampled components are inferred.
Main entry points: get_next_line.c Single-FD reader · get_next_line_bonus.c Multi-FD reader · get_next_line_utils.c Single-buffer utilities · get_next_line_utils_bonus.c FD buffer utilities
Components 8
Line readers
- Single-FD reader
get_next_line.c - Multi-FD reader
get_next_line_bonus.c
Buffer management
- Single-buffer utilities
get_next_line_utils.c - FD buffer utilities
get_next_line_utils_bonus.c - Single buffer state
get_next_line.h - Per-FD state
get_next_line_bonus.h
Stream I/O
- read syscall
Other components
- Library caller
Connections 10
- Library caller → Single-FD reader: calls
README.md - Single-FD reader → Library caller: returns line
README.md - Single-FD reader → read syscall: reads bytes
README.md - Single-FD reader → Single-buffer utilities: uses helpers
get_next_line.c - Single-FD reader → Single buffer state: uses state
get_next_line.c - Library caller → Multi-FD reader: calls
README.md - Multi-FD reader → Library caller: returns line
README.md - Multi-FD reader → read syscall: reads bytes
README.md - Multi-FD reader → FD buffer utilities: manages FD buffers
get_next_line_bonus.c - Multi-FD reader → Per-FD state: uses state
get_next_line_bonus.c