WMEMCMP(3POSIX)

💖 WMEMCMP(3POSIX) 💖

okay bestie, welcome to the POSIX Programmer's Manual — yes, the whole vibe, we're doing this 🫶

🌸 PROLOG 🌸

This manual page is part of the POSIX Programmer's Manual. Heads up tho, fr fr: the Linux implementation of this interface may differ (so if you're on Linux, go consult the corresponding Linux manual page for details of Linux behavior), or — plot twist — the interface may not be implemented on Linux at all. 😭 the audacity.

---

✨ NAME ✨

wmemcmp — compare wide characters in memory 🧠💅

---

🎀 SYNOPSIS 🎀

#include <wchar.h>

int wmemcmp(const wchar_t *ws1, const wchar_t *ws2, size_t n);

---

🦋 DESCRIPTION 🦋

So here's the tea. The functionality described on this reference page is aligned with the ISO C standard. Any conflict between the requirements described here and the ISO C standard is unintentional — no cap, nobody's trying to start drama. This volume of POSIX.1‐2017 defers to the ISO C standard.

The wmemcmp() function shall compare the first n wide characters of the object pointed to by ws1 to the first n wide characters of the object pointed to by ws2.

This function shall not be affected by locale, and all wchar_t values shall be treated identically. Translation: it does not care about your locale era, bestie, it treats every wchar_t the exact same way. 🌈

The null wide character and wchar_t values not corresponding to valid characters shall not be treated specially. Like, no favorites here, everybody's equal in this comparison. 👑

And if n is zero? Then the application shall ensure that ws1 and ws2 are valid pointers, and the function shall behave as if the two objects compare equal. (Yes, even with zero, those pointers gotta be valid. the way that zero still has rules 💀)

---

💜 RETURN VALUE 💜

The wmemcmp() function shall return an integer greater than, equal to, or less than zero — respectively — as the object pointed to by ws1 is greater than, equal to, or less than the object pointed to by ws2.

So: ws1 wins → positive. tie → zero. ws2 wins → negative. simple as that, main character energy ⭐

---

🙈 ERRORS 🙈

No errors are defined. (iconic, honestly, no problems just vibes)

The following sections are informative. (translation: the next few sections are bonus content, not requirements ✨)

---

🌟 EXAMPLES 🌟

None. 🍓

---

💅 APPLICATION USAGE 💅

None. 🎀

---

🧚 RATIONALE 🧚

None. 🦋

---

🔥 FUTURE DIRECTIONS 🔥

None. 💜

---

👑 SEE ALSO 👑

• wmemchr()
• wmemcpy()
• wmemmove()
• wmemset()

The Base Definitions volume of POSIX.1‐2017, <wchar.h>

---

🌈 COPYRIGHT 🌈

Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .

Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .

---

okay that's the whole page bestie, every last legal bit, you're welcome 🫶

and that's a wrap!! brought to you by IEEE/The Open Group, dated 2017, page WMEMCMP(3POSIX) — slay, periodt 💖✨