PUTWC(3POSIX)

✨ PUTWC β€” the putwc(3POSIX) page, but make it make sense πŸ’…

okay bestie, so this is a page from the POSIX Programmer's Manual β€” yes, that whole POSIX.1-2017 situation β€” and it's giving wide character goes onto a stream. Let's get into it 🫢


🌸 PROLOG 🌸

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 consult the corresponding Linux manual page for the actual Linux behavior, okay? Or, plot twist, the interface might not even be implemented on Linux at all. Rude, but true. πŸ’€


πŸŽ€ NAME πŸŽ€

putwc β€” put a wide character on a stream


⭐ SYNOPSIS ⭐

#include <stdio.h>
#include <wchar.h>

wint_t putwc(wchar_t wc, FILE *stream);

πŸ¦‹ DESCRIPTION πŸ¦‹

So the functionality described on this reference page is aligned with the ISO C standard. And like β€” any conflict between what's written here and the ISO C standard? Unintentional, fr fr. This volume of POSIX.1-2017 defers to the ISO C standard, periodt. πŸ‘‘

The putwc() function shall be equivalent to fputwc(), EXCEPT β€” and this is the tea β˜• β€” if it's implemented as a macro, it may evaluate stream more than once. Which means the argument should never be an expression with side-effects. Not even once. Do not do it. πŸ™ˆ


πŸ’– RETURN VALUE πŸ’–

Refer to fputwc(). That's it, that's the whole vibe. πŸ’«


🌈 ERRORS 🌈

Refer to fputwc(). Again β€” fputwc() has the answers, bestie. ✨

Also, quick note: the following sections are informative. (Meaning they're here for the lore, not the law. 🧚)


πŸ“ EXAMPLES πŸ“

None. Yeah. Zero. Nothing. The void. An empty group chat. 😭


πŸ’… APPLICATION USAGE πŸ’…

okay so here's the important part, and I need you to listen:

Since putwc() may be implemented as a macro, it may treat a stream argument with side-effects incorrectly. In particular:

putwc(wc,*f++)

need not work correctly. So... therefore, use of this function is not recommended. Instead, use fputwc(). That's the one. Use that one. 🫢


πŸ‘‘ RATIONALE πŸ‘‘

None. The committee said nothing, and honestly, iconic of them. πŸ’…


🌸 FUTURE DIRECTIONS 🌸

None. The future is unspecified and we're at peace with it. πŸ¦‹


πŸ”₯ SEE ALSO πŸ”₯

  • Section 2.5, Standard I/O Streams
  • fputwc()

And from The Base Definitions volume of POSIX.1-2017:

  • <stdio.h>
  • <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 β€” written by IEEE/The Open Group, 2017, for PUTWC(3POSIX). slay, stay hydrated, and please, for the love of everything, use fputwc() πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈπŸ’…πŸ«Ά