WCSCAT(3P)

📦 version 2017a, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, nixpkgs unstable, opensuse-leap 16.0

💖 WCSCAT(3P) — the POSIX Programmer's Manual, bestie edition 🎀

okay so welcome to WCSCAT(3P), straight out of the POSIX Programmer's Manual ✨ settle in, this one's short but it's a whole vibe.

🌸 PROLOG 🌸

Real talk first: this manual page is part of the POSIX Programmer's Manual. But heads up, bestie 💅 — the Linux implementation of this interface may differ (so go consult the corresponding Linux manual page for the deets on Linux behavior), or honestly? the interface might not even be implemented on Linux at all. no cap. 🙈

👑 NAME 👑

wcscat — concatenate two wide-character strings 🦋

✨ SYNOPSIS ✨

#include <wchar.h>

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

look at that signature. iconic. 💅

💜 DESCRIPTION 💜

The functionality described on this reference page is aligned with the ISO C standard. If there's any conflict between what's written here and the ISO C standard, that's unintentional, fr fr — this volume of POSIX.1‐2017 defers to the ISO C standard. periodt. 👑

So what does wcscat() actually do, you ask? She appends 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. it's giving "scoot over, I'm sitting here now" 🫶

⚠️ and now the scary part, bestie: if copying takes place between objects that overlap, the behavior is undefined. undefined behavior is not a vibe check you want to fail. keep your buffers separate, okay? 😭

🌈 RETURN VALUE 🌈

wcscat() shall return ws1. that's it. that's the return value. and ngl, no return value is reserved to indicate an error — so don't go looking for an error code, she doesn't have one to give you 💀

🧚 ERRORS 🧚

No errors are defined. none. zero. nada. slay. ✨

The following sections are informative — meaning they're the lil bonus content, not the main character energy rules. 🌸

🍓 EXAMPLES 🍓

None. 🙈

🎀 APPLICATION USAGE 🎀

None. 💜

⭐ RATIONALE ⭐

None. 💅

🦋 FUTURE DIRECTIONS 🦋

None. 🌈

🔥 SEE ALSO 🔥

  • wcsncat()
  • The Base Definitions volume of POSIX.1‐2017, <wchar.h>

iykyk, go read those too bestie, they're part of the lore 📚

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 🫶 this lil gem came to you courtesy of IEEE/The Open Group, 2017, and the page itself is WCSCAT(3P). go forth and concatenate responsibly, mwah 💋💅✨

📦 where this page comes from