funclose(3)

💖 funclose(3) — the SAORD Documentation glow-up 💖

okay bestie, so this is the funclose page from the SAORD Documentation set, and honestly? it's short, it's sweet, and it's lowkey the most important cleanup ritual in your Funtools era. let's get into it ✨

✨ NAME ✨

FunClose — close a Funtools data file 🎀

like. that's it. that's the job. she closes files. she frees things. she's the friend who actually turns off the lights when everyone leaves. 💅

🌸 SYNOPSIS 🌸

#include <funtools.h>

void FunClose(Fun fun)

yes bestie, that's the whole signature. one arg. no return value. she doesn't give you a status code, she doesn't text back, she just does it. 🫶

🦋 DESCRIPTION 🦋

so the FunClose() routine closes a previously-opened Funtools data file, and it also frees the control structures — like, it's not just closing the door, it's doing a full spring clean on the way out. no ghost data structures haunting your memory. we love to see it. 😌✨

now here's the part where you need to pay attention, because it's giving plot twist:

if a Funtools reference handle was passed to the FunOpen() call for this file, AND if copy mode also was specified for that file, then FunClose() will also copy the remaining extensions from the input file to the output file — but ONLY if the input file is still open. 👀

so yeah. two conditions have to hit for the copy magic to happen: the reference handle was passed to FunOpen(), and copy mode was specified for that file. and the input file needs to still be open for those remaining extensions to actually get copied over. no open input file, no copy. periodt. 💀

which is exactly why the recommendation is:

always close the output Funtools file before the input file. 🎀

like, output first, then input. that's the order. that's the vibe check. don't be out here closing the input first and then wondering why your extensions ghosted you. 🙈

and if you can't do it in that order for whatever reason? no stress, you have options:

• you can call FunFlush() explicitly instead — that's the alternative route, and it's right there waiting for you 💚

so to recap the whole ~situation~: close output, then input, or flush manually. either way, somebody's gotta handle the extensions, and it's not gonna be future-you at 2am. 😭

👑 SEE ALSO 👑

• See funtools(7) for a list of Funtools help pages 📚

like, go read the whole funtools(7) situation if you want the full lore. it's the master doc, the main character of the help pages, the one that has the receipts. 🔥

and that's the page bestie!! this was funclose(3) from version 1.4.5, dated April 14, 2011 — yeah she's an oldie but she's still out here closing files and freeing control structures like the icon she is. ⭐ close your outputs before your inputs, call FunFlush() if you must, and go slay 💅💖