TT_ERROR(3)

🎀 tt_error — capture ToolTalk function errors 🎀

okay bestie, welcome to the library call page for tt_error — yes, the one that helps you capture ToolTalk function errors. 💅

✨ NAME ✨

tt_error — capture ToolTalk function errors

✨ SYNOPSIS ✨

#include &<Tt/tt_c.h>
void tt_error(
const char *funcname,
Tt_status status);

💖 DESCRIPTION 💖

The tt_error function is a publicly-known null function. It gets called by the ToolTalk library just before it returns from any ToolTalk API call that has a status other than TT_OK. The caller passes the name of the function that’s about to return and the function’s status code. 🫶

You can use this function to set a dbx breakpoint to quickly catch and trace back any ToolTalk errors. You can also interpose this function, for example, to log ToolTalk errors to stderr. no cap, that’s the whole flex. ✨

🧚 ARGUMENTS 🧚

• funcname — specifies the name of the function. 💖
• status — specifies the function’s return status value. 🦋

🌸 RETURN VALUE 🌸

None. Literally none, bestie. 💀

👑 APPLICATION USAGE 👑

The following code example shows how an application might interpose this function to log ToolTalk errors to stderr:

void tt_error(const char *funcname, Tt_status status) {
        fprintf(stderr, "ToolTalk function %s returned %s.0,
                funcname, tt_status_message(status));
}

periodt — that’s the exact example from the page. 💅

🦋 SEE ALSO 🦋

• Tt/tt_c.h - Tttt_c(5)

---

okay that’s the tea, bestie — the footer/source line is tt_error(library call), and there’s no separate version or date stamp printed here, so I’m not inventing one. mwah 💋