AL_GET_FIRST_CONFIG_ENTRY(3)

💅 al_get_first_config_entry(3) — the Allegro 5 API, but make it make sense

okay bestie, so this one is from the Library Functions Manual and it's literally your entry point into reading config keys 🎀

---

✨ NAME ✨

al_get_first_config_entry — Allegro 5 API. that's her. that's the whole name. slay.

---

🌸 SYNOPSIS 🌸

#include <allegro5/allegro.h>

char const *al_get_first_config_entry(ALLEGRO_CONFIG const *config,
   char const *section, ALLEGRO_CONFIG_ENTRY **iterator)

yes the **iterator is double-starred, she's a pointer to a pointer, do not come for her 💅

---

💖 DESCRIPTION 💖

so what does she actually do? she hands you back the name of the first key in the section you picked, inside the config you passed in. that's it. that's the vibe 🦋

and if that section is empty? you get NULL back, no keys, nothing, an empty inbox, we've all been there 😭

the iterator works exactly like the one over in al_get_first_config_section(3) — same energy, different function, iykyk ✨

⚠️ real talk though, listen to me: the returned string and the iterator are only valid as long as no change is made to the passed ALLEGRO_CONFIG(3). like, the second you go mutating that config, they're toast. don't touch the config, don't lose your pointers, periodt 💀

---

🔥 SEE ALSO 🔥

• al_get_next_config_entry(3) — the next one in the chain, she's got a whole lineup 🫶

---

alright bestie that's the page!! 🌈 this was the Allegro reference manual coming at you with the al_get_first_config_entry(3) entry, no date on the footer to give you, so take the source and run with it 💜✨