XtErrorMsg(3)

💖 XtErrorMsg(3) — XT COMPATIBILITY FUNCTIONS 💖

okay bestie, we're in the X Toolkit Intrinsics manual, section 3, and today's topic is high-level error handlers ✨ the little squad of functions that goes by the name XtErrorMsg, XtSetErrorMsgHandler, XtWarningMsg, and XtSetWarningMsgHandler. yes that's four whole names in one NAME line, they're a package deal, we don't split them up 🫶

---

✨ NAME ✨

XtErrorMsg, XtSetErrorMsgHandler, XtWarningMsg, XtSetWarningMsgHandler — high-level error handlers 💅

---

🌸 SYNTAX 🌸

first things first, you gotta pull in the header or none of this exists:

#include <X11/Intrinsic.h>

then the four icons themselves:

_X_NORETURN void XtErrorMsg(const char *name, const char *type, const
       char *class, const char *defaultMsg, String *params, Cardinal
       *num_params);

void XtSetErrorMsgHandler(_X_NORETURN XtErrorMsgHandler msg_handler);

void XtSetWarningMsgHandler(XtErrorMsgHandler msg_handler);

void XtWarningMsg(const char *name, const char *type, const char *class,
       const char *defaultMsg, String *params, Cardinal *num_params);

not me pointing out that _X_NORETURN on XtErrorMsg and on the XtErrorMsgHandler in XtSetErrorMsgHandler — that's the compiler being told "this thing does NOT come back." it's giving final girl energy 💀

---

🎀 ARGUMENTS 🎀

• class — the resource class of the error message. yes, it has a class, it's fancy like that 👑
• default — the default message to use. the fallback fit, the backup outfit 💖
• name — the general kind of error. the vibe category, if you will ✨
• type — the detailed name of the error. like name but with receipts 🔍
• msg_handler — the new fatal error procedure, which should not return, or the nonfatal error procedure, which usually returns. literally the whole personality of the handler in one arg 😭
• num_params — the number of values in the parameter list. count 'em 🔢
• params — a pointer to a list of values to be stored in the message. the little payload that gets tucked into the message 🎁

---

🦋 DESCRIPTION 🦋

okay so here's the tea, and it's a whole superseded situation, no cap:

• The XtErrorMsg function has been superseded by XtAppErrorMsg. 👋
• The XtSetErrorMsgHandler function has been superseded by XtAppSetErrorMsgHandler. 👋
• The XtSetWarningMsgHandler function has been superseded by XtAppSetWarningMsgHandler. 👋
• The XtWarningMsg function has been superseded by XtAppWarningMsg. 👋

fr fr, all four of these got replaced. they're the older generation of the family — still here, still valid, but the XtApp* versions are the main characters now. if you're writing new code, lowkey go say hi to the XtApp crew instead 💅

---

🌈 SEE ALSO 🌈

go read these too, bestie, they're all connected:

• XtAppErrorMsg(3)
• X Toolkit Intrinsics - C Language Interface
• Xlib - C Language X Interface

---

and that's the whole page, periodt ✨ this was X Version 11, libXt 1.3.1, and we've been living in XtErrorMsg(3) the entire time 🦋💖 go forth and handle your errors, you absolute icon 🫶🎀