WMEMCHR(3P)

💖 WMEMCHR(3P) 💖

ok so bestie, welcome to wmemchr from the POSIX Programmer's Manual — yes, the 3P one, not the Linux one. sit down, grab a lil snack, we're gonna go through this together ✨

---

🌸 PROLOG 🌸

okay so before literally anything else: this manual page is part of the POSIX Programmer's Manual. the Linux implementation of this interface may differ — like, consult the corresponding Linux manual page for details of Linux behavior, fr fr. or… the interface may not be implemented on Linux at all 🙈. vibe check passed? cool, moving on.

---

👑 NAME 👑

wmemchr — find a wide character in memory 🔍

---

✨ SYNOPSIS ✨

#include <wchar.h>

wchar_t *wmemchr(const wchar_t *ws, wchar_t wc, size_t n);

she's short, she's sweet, she's giving main character energy 💅

---

🦋 DESCRIPTION 🦋

so the functionality described on this reference page is aligned with the ISO C standard. and if there's any conflict between the requirements described here and the ISO C standard? that conflict is unintentional, not me being messy. this volume of POSIX.1‐2017 defers to the ISO C standard. periodt.

now the actual tea: the wmemchr() function shall locate the first occurrence of wc in the initial n wide characters of the object pointed to by ws.

and here's the part that lowkey slays — this function shall not be affected by locale, and all wchar_t values shall be treated identically. the null wide character and wchar_t values that don't correspond to valid characters shall not be treated specially. no favorites, no special treatment, everyone's equal in this function's eyes 💖

and if n is zero? the application shall ensure that ws is a valid pointer, and the function behaves as if no valid occurrence of wc is found. like, valid pointer still required bestie, don't play games 🙏

---

🎀 RETURN VALUE 🎀

the wmemchr() function shall return a pointer to the located wide character, or a null pointer if the wide character does not occur in the object. that's it. that's the whole thing. simple queen behavior 👑

---

💀 ERRORS 💀

No errors are defined.

and then it says, and I quote, "The following sections are informative." so everything after this is basically bonus content, not requirements. noted 🫶

---

🌈 EXAMPLES 🌈

None.

like literally none. iconic of them honestly.

---

🍓 APPLICATION USAGE 🍓

None.

again. nothing. the page said "no thoughts, head empty" ✨

---

🧚 RATIONALE 🧚

None.

they gave us nothing and we ate it up anyway 💅

---

⭐ FUTURE DIRECTIONS ⭐

None.

the future is bright and also empty. we love that for us.

---

🔥 SEE ALSO 🔥

• wmemcmp()
• wmemcpy()
• wmemmove()
• wmemset()

and also — the Base Definitions volume of POSIX.1‐2017, <wchar.h> 📚

the whole wide-memory squad, all together, no cap.

---

💜 COPYRIGHT 💜

okay bestie, legal moment, stay with me:

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. so if there's drama, the original wins, no debate. 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 .

---

ngl if you spotted a typo, it's probably a conversion thing, not a real lore drop 🙈

---

IEEE/The Open Group — 2017 🎀

and that's the whole page bestie!! WMEMCHR(3P), brought to you by the 2017 girlies at IEEE/The Open Group. mwah 💋✨