GENDERS_NODELIST_CREATE(3)

💖 GENDERS_NODELIST_CREATE 💖

okay bestie, so this is the LIBGENDERS page for the list create / clear / destroy girlies ✨ — yes, the whole squad is here, genders_nodelist_create and all her sisters. Sit down, grab a boba, we're doing list management. 🎀

---

🌸 NAME 🌸

genders_nodelist_create, genders_nodelist_clear, genders_nodelist_destroy, genders_attrlist_create, genders_attrlist_clear, genders_attrlist_destroy, genders_vallist_create, genders_vallist_clear, genders_vallist_destroy — the list create, clear, and destroy routines. the whole little family. 🫶

---

✨ SYNOPSIS ✨

#include <genders.h>

int genders_nodelist_create(genders_t handle, char ***nodelist);

int genders_nodelist_clear(genders_t handle, char **nodelist);

int genders_nodelist_destroy(genders_t handle, char **nodelist);

int genders_attrlist_create(genders_t handle, char ***attrlist);

int genders_attrlist_clear(genders_t handle, char **attrlist);

int genders_attrlist_destroy(genders_t handle, char **attrlist);

int genders_vallist_create(genders_t handle, char ***vallist);

int genders_vallist_clear(genders_t handle, char **vallist);

int genders_vallist_destroy(genders_t handle, char **vallist);

---

🦋 DESCRIPTION 🦋

so like. these nine functions? they're the ones that make, wipe, and yeet lists — and a "list" here is literally just an array of strings, no cap. you use them with genders_getnodes(3), genders_getattr(3), and genders_getattr_all(3). it's giving ✨plumbing✨ but the good kind. 💅

creating — genders_nodelist_create(), genders_attrlist_create(), and genders_vallist_create() each create a list with the minimum size needed to store nodes, attributes, and attribute values respectively. nodelist, attrlist, and vallist are respectively set to point to the created list. and here's the slay part: the created lists are guaranteed to store all the node, attribute, and value information returned from genders_getnodes(3), genders_getattr(3), and genders_getattr_all(3). guaranteed. iconic. 👑

clearing — genders_nodelist_clear(), genders_attrlist_clear(), and genders_vallist_clear() clear any information stored in the lists pointed to by nodelist, attrlist, and vallist respectively. do you have to call them right after the create functions? no bestie. 🚫 they only have to be called after the list was used in genders_getnodes(3), genders_getattr(3), and genders_getattr_all(3), and the programmer wishes to re-use the list. that's it, that's the rule.

destroying — genders_nodelist_destroy(), genders_attrlist_destroy(), and genders_vallist_destroy() destroy the lists pointed to by nodelist, attrlist, and vallist respectively. closure. 🧚

⚠️ and now the plot twist, and it's a big one: if no attributes or values are listed in the genders database, all of the attrlist and vallist functions will do nothing. like, nothing nothing. and the pointer you passed into genders_attrlist_create() and genders_vallist_create() will not be set. so don't be out here dereferencing it and acting surprised, i'm begging 😭

---

🌈 RETURN VALUES 🌈

on success, genders_nodelist_create(), genders_attrlist_create(), and genders_vallist_create() return the number of elements the created list can store. so you know exactly how much room you've got, which is lowkey thoughtful of them. 💖

on success, genders_nodelist_clear(), genders_attrlist_clear(), genders_vallist_clear(), genders_nodelist_destroy(), genders_attrlist_destroy(), and genders_vallist_destroy() return 0. zero. nothing. clean. ✨

on error, -1 is returned, and an error code is returned in handle. you can grab that error code with genders_errnum(3), and a description of it with genders_strerror(3). and where do the error codes live? in genders.h. periodt. 📚

---

💀 ERRORS 💀

• GENDERS_ERR_NULLHANDLE — the handle parameter is NULL. the genders handle must be created with genders_handle_create(3). you cannot run this on vibes alone bestie, you need an actual handle 🙈
• GENDERS_ERR_NOTLOADED — genders_load_data(3) has not been called to load genders data. before lists of appropriate size can be created, the genders file must be read and parsed. no data, no list, that's just how it is 🍓
• GENDERS_ERR_PARAMETERS — an incorrect parameter has been passed in. something's wrong with what you handed over 😭
• GENDERS_ERR_NULLPTR — a null pointer has been found in the list passed in. girl. there's a NULL in the list 💀
• GENDERS_ERR_OUTMEM — malloc(3) has failed internally, system is out of memory. the machine is tired. it's not you, it's the RAM. 😔
• GENDERS_ERR_MAGIC — handle has an incorrect magic number. handle does not point to a genders handle, or handle has been destroyed by genders_handle_destroy(3). the magic is ✨not✨ there, and you cannot fake it 🔮

---

🎀 FILES 🎀

• /usr/include/genders.h

---

👑 SEE ALSO 👑

• libgenders(3)
• genders_handle_create(3)
• genders_load_data(3)
• genders_getnodes(3)
• genders_getattr(3)
• genders_getattr_all(3)
• genders_errnum(3)
• genders_strerror(3)

---

and that's the whole page bestie, no notes 💅 this masterpiece was brought to you by LLNL, dated August 2003 (yes it's older than us, it ate and left no crumbs), sitting in the LIBGENDERS collection. go forth and manage your lists responsibly. mwah 🫶💖✨