VWSCANF(3P)

πŸ’– VWSCANF(3P) β€” the wide-char scanf-but-with-a-va_list situation πŸ’–

okay bestie, gather round, because we're reading a page straight out of the POSIX Programmer's Manual (that's the manual name, she's fancy) and she's a short one but she's iconic πŸ’…


✨ PROLOG ✨

so like, real talk first 🫢 β€” this manual page is part of the POSIX Programmer's Manual. But heads up:

  • the Linux implementation of this interface may differ β€” like, go consult the corresponding Linux manual page for the deets on Linux behavior, fr fr
  • or honestly? the interface may not be implemented on Linux at all πŸ’€

so don't come for me if it's giving "not found", okay?


🌸 NAME 🌸

vwscanf β€” wide-character formatted input of a stdarg argument list

that's it. that's the whole vibe. wide characters, formatted input, and a stdarg argument list. main character energy only ✨


πŸŽ€ SYNOPSIS πŸŽ€

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

int vwscanf(const wchar_t *restrict format, va_list arg);

look at her πŸ₯Ή three includes, one function, zero drama. slay.


πŸ¦‹ DESCRIPTION πŸ¦‹

bestie, this one is a referral, not a whole essay:

Refer to vfwscanf().

that's it. that's the description. the way that this page simply delegates 😭 go read vfwscanf() and she'll tell you everything you need. no cap.


okay so this is the part where we give credit where credit is due, because we do NOT steal content in this house πŸ’œ

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 .

Also, real talk: 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 .

like, the errors are probably from the conversion, not from the actual standard, so be nice πŸ™ˆ


and that's the whole page, bestie πŸ“ IEEE/The Open Group, 2017 β€” that's the source and the date, mwah, bye πŸ§šπŸ’–βœ¨

πŸ“¦ where this page comes from