WCSNCAT(3P)

✨ WCSNCAT(3P) ✨ β€” bestie edition πŸ’–

okay so this one lives in the POSIX Programmer's Manual, and it's giving "the standard wrote this, not your distro." 🫢

🌸 PROLOG 🌸

Real talk: this manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (so like, go read the corresponding Linux manual page for the tea on Linux behavior), or the interface may not even be implemented on Linux at all. πŸ’€


πŸ‘‘ NAME πŸ‘‘

wcsncat β€” concatenate a wide-character string with part of another. no cap, that's the whole job. ✨


πŸŽ€ SYNOPSIS πŸŽ€

#include <wchar.h>

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

πŸ’… DESCRIPTION πŸ’…

So 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 β€” nobody's trying to start drama. This volume of POSIX.1‐2017 defers to the ISO C standard. periodt. πŸ‘‘

The wcsncat() function shall append not more than n wide-character codes from the array pointed to by ws2 to the end of the wide-character string pointed to by ws1. and bestie, listen β€” a null wide-character code and the wide-character codes that follow it are not appended. so if ws2 hits a null early, that's it, we stop. πŸ›‘

The initial wide-character code of ws2 shall overwrite the null wide-character code at the end of ws1. iconic behavior tbh. and a terminating null wide-character code shall always be appended to the result. πŸ’–

⚠️ If copying takes place between objects that overlap, the behavior is undefined. not "kinda weird," not "maybe fine" β€” undefined. don't do it, bestie. 😭

πŸ¦‹ RETURN VALUE πŸ¦‹

wcsncat() shall return ws1. that's it. no return value is reserved to indicate an error β€” there's no secret error code hiding in there, it's just your string back. πŸ’«


🌈 ERRORS 🌈

No errors are defined. none. zero. the void. πŸ™ˆ

The following sections are informative β€” aka, the vibe is "we're just chatting now," not "this is normative." 🫢


πŸ“ EXAMPLES πŸ“

None. 😭 (yes really, nothing here)


🧚 APPLICATION USAGE 🧚

None. πŸ’œ


⭐ RATIONALE ⭐

None. πŸŽ€


🌸 FUTURE DIRECTIONS 🌸

None. ✨


πŸ”₯ SEE ALSO πŸ”₯

  • wcscat()

Also, the Base Definitions volume of POSIX.1‐2017, <wchar.h>. iykyk. πŸ’…


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. (yes, the original is the one holding the whistle 🏁) 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, no notes. this one's from IEEE/The Open Group, dated 2017 β€” mwah, thanks for reading, go forth and concatenate responsibly. πŸ’…βœ¨πŸ«Ά

πŸ“¦ where this page comes from