hook_config_section(3)

✨ NAME ✨

hook_config_section — hooks a config file section with your own custom handlers, bestie 💖 Part of the Allegro game programming library, iykyk.

🎀 SYNOPSIS 🎀

#include <allegro.h>

void hook_config_section(const char *section, int (*intgetter)(const
char *name, int def), const char *(*stringgetter)(const char *name,
const char *def), void (*stringsetter)(const char *name, const char
*value));

🦋 DESCRIPTION 🦋

Okay so basically? You're taking control of the config file section named in section, and from that point on it's your hook functions doing the work — not the normal disk file access. You're the main character now, the file is just vibing in the background 💅

If both the getter and setter functions are NULL, then a currently present hook gets unhooked. Simple as that.

Hooked functions have the highest priority — like, no cap, top of the food chain 👑

And if a section is hooked, the hook is always called. Which means you can even hook a '#' section, because not even override_config_file() can override a hooked section. That's the power, bestie ⭐

Example time, look how cute this is:

int decode_encrypted_int(const char *name, int def)
{
   ...
}

const char *decode_encrypted_string(const char *name, const char *def)
{
   ...
}

void encode_plaintext_string(const char *name, const char *value)
{
   ...
}

int main(int argc, char *argv[])
{
   ...
   /* Make it harder for users to tinker with the high scores. */
   hook_config_section("high_scores", decode_encrypted_int,
      decode_encrypted_string, encode_plaintext_string);
   ...
} END_OF_MAIN()

The way that comment just says it plainly — "make it harder for users to tinker with the high scores" 😭 protect your leaderboard, queen. Obsessed.

🌈 SEE ALSO 🌈

• config_is_hooked(3)

And that's the whole vibe! 🫶 This little love letter to your config files came to you courtesy of the Allegro manual, version 4.4.3, and the page was called hook_config_section(3) — go forth and hook responsibly, mwah 💋🌸