WMEMCPY(3P)

πŸ’– WMEMCPY(3P) β€” POSIX Programmer's Manual πŸ’–

okay bestie, so this one is wmemcpy, and it lives in the POSIX Programmer's Manual (that's the 3P in the title, iykyk). πŸŽ€


🌸 PROLOG 🌸

Real talk before we start: this manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ β€” so if you're on Linux, go consult the corresponding Linux manual page for details on Linux behavior. Or, plot twist, the interface may not be implemented on Linux at all. πŸ™ˆ So like… vibe check your platform first, fr fr.


✨ NAME ✨

wmemcpy β€” copy wide characters in memory πŸ¦‹


πŸ’… SYNOPSIS πŸ’…

#include <wchar.h>

wchar_t *wmemcpy(wchar_t *restrict ws1, const wchar_t *restrict ws2,
    size_t n);

look at her. so clean. so iconic. πŸ‘‘


🫢 DESCRIPTION 🫢

okay so the functionality on this reference page is aligned with the ISO C standard. If there's any conflict between the requirements described here and the ISO C standard, that conflict is unintentional β€” and this volume of POSIX.1‐2017 defers to the ISO C standard. periodt.

The wmemcpy() function shall copy n wide characters from the object pointed to by ws2 to the object pointed to by ws1. πŸ’«

Now here's the part that's lowkey the whole personality of this function: it 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. Like, she does not care. she does not judge. she copies bytes-adjacent wide characters and moves on. πŸ’…

And if n is zero? Then the application shall ensure that ws1 and ws2 are valid pointers, and the function shall copy zero wide characters. Zero. Nothing. A whole lot of nothing. But the pointers still gotta be valid, bestie β€” no shortcuts. πŸŽ€


⭐ RETURN VALUE ⭐

wmemcpy() shall return the value of ws1. That's it. That's the tea. πŸ“


πŸ’€ ERRORS πŸ’€

No errors are defined. Not one. She simply does not have an error era. ✨

The following sections are informative. (yes, that's a real line, we keep it, slay.)


🌈 EXAMPLES 🌈

None. 😭


🧚 APPLICATION USAGE 🧚

None. πŸ™ˆ


πŸ’œ RATIONALE πŸ’œ

None. 🫢


πŸ¦‹ FUTURE DIRECTIONS πŸ¦‹

None. πŸ’–


πŸ‘‘ SEE ALSO πŸ‘‘

  • wmemchr()
  • wmemcmp()
  • wmemmove()
  • wmemset()

Also the Base Definitions volume of POSIX.1‐2017, <wchar.h> β€” go read the header, she's got lore. 🌸


okay legal bestie moment, gotta be precise here:

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 .

tl;dr: if this page and the actual standard disagree, the standard wins. always. no cap.

and that's the whole page, bestie!! brought to you by IEEE/The Open Group, 2017 β€” mwah, love u, go copy some wide characters responsibly πŸ’–βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from