LIBMAWK_I...IZE_STAGE(3libmawk)

💖 LIBMAWK_INITIALIZE_STAGE* 💖

okay bestie, welcome to the libmawk manual, section 3libmawk — this one's all about spinning up a brand new libmawk context in three ✨stages✨ instead of one big gulp. it's giving controlled chaos, and we're obsessed. 🦋

🌸 NAME 🌸

libmawk_initialize_stage* — create a new libmawk context in 3 stages

🎀 SYNOPSIS 🎀

#include <libmawk.h>

mawk_state_t *libmawk_initialize_stage1(void);

mawk_state_t *libmawk_initialize_stage2(mawk_state_t * m,int s ,char*"argv[]);

mawk_state_t *libmawk_initialize_stage3(mawk_state_t * m);

(yes, that char*"argv[] is literally what it says, we do not touch the sacred text 💅)

✨ DESCRIPTION ✨

so the libmawk_initialize_stage*() functions, when you put all three together, do exactly the same thing as libmawk_initialize() — but they let your application slide in and do stuff between the stages. main character energy, honestly. 👑

libmawk_initialize_stage1() hands you back a pointer to a freshly created libmawk context. and no cap, you can have any number of libmawk contexts living in parallel inside one application. it's a whole friend group. 🫶

libmawk_initialize_stage2() is what you call after a successful stage1 call. Stage2 is the one responsible for processing the command line arguments and loading any script. 📜

the arguments are the same as for a command line mawk session, periodt. scripts get loaded (either straight from the command line or from files using -f), variables get set (with -v), special options get set (with -W), etc. but here's the slay: unlike with libmawk_initialize(), your application is allowed to just... not provide any script at this stage. all command line arguments are processed regardless. 🙈

the most common case, fr fr, is that the application calls stage1 with no script, and then — because it already has a context — does some manipulations on it. for example, registering some C functions that would already get called in the BEGIN part of the script that's gonna be loaded later. iconic behavior. 💅

optionally, before calling stage2, the application loads the actual script(s) using mawk_append_input_file().

libmawk_initialize_stage3() is the grand finale of the three-stage initialization process. Stage3 is responsible for running all the BEGIN parts of all scripts loaded at stage1 or stage2. 🔥

and the reason it's a separate call? so your application can manipulate the context right before initializing the scripts. it's giving "let me fix my hair before the photo". 📸

Stage2 gets the pointer that stage1 returned, and stage3 gets the pointer that stage2 returned. subsequent calls to libmawk functions should get the pointer that stage3 returned. chain of custody, bestie. 🔗

⭐ RETURN VALUE ⭐

• at stage 1: a pointer to a new libmawk context, or NULL on error. 😭
• subsequent stages: they return that same pointer, or NULL on error.

ngl if you get NULL back, something went wrong — that's your vibe check failing. 💀

🌈 SEE ALSO 🌈

• libmawk_initialize_stage(3libmawk)
• libmawk_uninitialize(3libmawk)
• mawk_append_input_file(3libmawk)

and that's the whole page, bestie — go forth and initialize responsibly. this was the libmawk manual, section 3libmawk, dated 2009-08-10, and honestly it ate. 💖✨🎀 bye!! 🦋🌸