AUPARSE_NEXT_RECORD(3)

💖 NAME 💖

auparse_next_record — move record cursor, bestie ✨

---

🎀 SYNOPSIS 🎀

#include <auparse.h>

int auparse_next_record(auparse_state_t *au);"

---

🌸 DESCRIPTION 🌸

okay so picture this: the library has these internal cursors, right? and auparse_next_record is literally just the glow-up move that slides those cursors over to point at the next record of the current event. that's it. that's the whole job. slay 💅

but bestie. listen. 🫶

do NOT call this function from a feed interface callback function. the way that will deadlock the code 😭 like, full stop, everything just sits there. not cute, not iconic, absolutely not the vibe.

so if you're in that scenario (iykyk), the move is: check how many records are in the current event with auparse_get_num_records first, and only call this if there are actually more records left. vibe check before you commit, periodt ✨

---

🔥 RETURN VALUE 🔥

• -1 — something went wrong, an error happened 😭
• 0 — no more records in the current event, that's a wrap 🎬
• 1 — success!! we ate 👑

---

🦋 SEE ALSO 🦋

• auparse_next_event(3)
• auparse_get_num_records(3)

---

👑 AUTHOR 👑

Steve Grubb 💜 (giving main character energy fr fr)

---

and that's the whole page, bestie — this came out of Red Hat back in Feb 2007, so it's been serving correct cursor-moving realness for literal decades 🎀✨ no cap.