VFWSCANF(3P)

πŸ’– VFWSCANF(3P) β€” the wide-character formatted input girlies πŸ’–

okay bestie, welcome to the POSIX Programmer's Manual ✨ this one is called VFWSCANF(3P) and it is literally about reading formatted wide-character input from a stdarg argument list. yes we're doing variadic girl math today. let's go πŸŽ€


🌸 PROLOG 🌸

okay so before anything else, real talk: this manual page is part of the POSIX Programmer's Manual. the Linux implementation of this interface may differ β€” so pls 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. vibe check accordingly 🫢


✨ NAME ✨

vfwscanf, vswscanf, vwscanf β€” wide-character formatted input of a stdarg argument list. that's the whole gig. three little icons, one shared destiny πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

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

int vfwscanf(FILE *restrict stream, const wchar_t *restrict format,
    va_list arg);
int vswscanf(const wchar_t *restrict ws, const wchar_t *restrict format,
    va_list arg);
int vwscanf(const wchar_t *restrict format, va_list arg);

look at those signatures. restrict everywhere. she's committed to the bit. πŸ‘‘


πŸ’– 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 β€” no drama intended, fr fr. this volume of POSIX.1‐2017 defers to the ISO C standard. periodt.

okay so the main character energy:

the vfwscanf(), vswscanf(), and vwscanf() functions shall be equivalent to the fwscanf(), swscanf(), and wscanf() functions, respectively β€” except that instead of being called with a variable number of arguments, they are called with an argument list as defined in the <stdarg.h> header. same energy, different delivery mechanism πŸ’«

  • these functions shall not invoke the va_end macro.
  • as these functions invoke the va_arg macro, the value of ap after the return is unspecified. so like… don't go peeking at ap afterwards, she's not gonna tell you what she is anymore πŸ™ˆ

πŸ”₯ RETURN VALUE πŸ”₯

refer to fwscanf(). that's it. that's the section. go ask her sister πŸ’…


πŸ’€ ERRORS πŸ’€

refer to fwscanf().

the following sections are informative. (translation: the lore continues but it's optional reading, iykyk)


🌈 EXAMPLES 🌈

None.

not a single one. we are starving. no examples, no crumbs, nothing 😭


🫢 APPLICATION USAGE 🫢

applications using these functions should call va_end(ap) afterwards to clean up. yes bestie, clean up after yourself. leave the function the way you'd want to find it. self-care is calling va_end πŸ§–β€β™€οΈ


⭐ RATIONALE ⭐

None.

the reasoning is a mystery. iconic of her honestly.


🧚 FUTURE DIRECTIONS 🧚

None.

she's not going anywhere. she's not changing. she IS the moment.


🌸 SEE ALSO 🌸

  • Section 2.5, Standard I/O Streams, fwscanf()
  • The Base Definitions volume of POSIX.1‐2017, <stdarg.h>, <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 babes πŸŽ€ brought to you by IEEE/The Open Group, 2017 β€” yeah that's the source and the date, we're keeping receipts. VFWSCANF(3P) forever. slay, stay variadic, and always call va_end πŸ’…βœ¨

πŸ“¦ where this page comes from