WCSCAT(3POSIX)

πŸ’– WCSCAT β€” the POSIX girlies' guide to gluing wide strings together πŸ’–

okay so bestie, welcome to wcscat(3POSIX), straight outta the POSIX Programmer's Manual 🫢


🌸 PROLOG 🌸

so like, real talk first: 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 peek at the corresponding Linux manual page for the actual tea on Linux behavior. and honestly? the interface might not even be implemented on Linux at all. πŸ’€ it's giving "check before you ship".


✨ NAME ✨

wcscat β€” concatenate two wide-character strings

(like strcat but the wide-character girlies' version, no cap)


πŸŽ€ SYNOPSIS πŸŽ€

#include <wchar.h>

wchar_t *wcscat(wchar_t *restrict ws1, const wchar_t *restrict ws2);

πŸ’… DESCRIPTION πŸ’…

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. This volume of POSIX.1‐2017 defers to the ISO C standard. periodt.

now the actual vibe: wcscat() shall append a copy of the wide-character string pointed to by ws2 β€” including the terminating null wide-character code β€” to the end of the wide-character string pointed to by ws1. 🌈

The initial wide-character code of ws2 shall overwrite the null wide-character code at the end of ws1. so basically ws2 slides in and takes that null's spot. iconic behavior honestly.

⚠️ bestie. If copying takes place between objects that overlap, the behavior is undefined. undefined. not "weird", not "kind of off" β€” undefined. do not do it. this is not a drill πŸ™ˆ

πŸ”₯ RETURN VALUE πŸ”₯

wcscat() shall return ws1. that's it. that's the whole return value.

and no β€” no return value is reserved to indicate an error. so don't go checking the return for a lil error code, there isn't one. it just hands you ws1 back and expects you to have handled your business beforehand. πŸ’€


πŸ‘‘ ERRORS πŸ‘‘

No errors are defined.

The following sections are informative.


πŸ¦‹ EXAMPLES πŸ¦‹

None.


🌸 APPLICATION USAGE 🌸

None.


⭐ RATIONALE ⭐

None.


🌈 FUTURE DIRECTIONS 🌈

None.


πŸ’œ SEE ALSO πŸ’œ

  • wcsncat()

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


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 .


and that's the whole page bestie, ty for coming to my TED talk πŸ’– mwah. this lil masterpiece is brought to you by IEEE/The Open Group, 2017, and the page itself is WCSCAT(3POSIX) β€” go forth and concatenate responsibly, and remember: overlapping objects are the enemy 🧚✨