VFWSCANF(3POSIX)

📦 version 2017a, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu resolute, ubuntu stonking

🌸 VFWSCANF(3POSIX) — the POSIX Programmer's Manual, bestie edition 🌸

ok so you found the vfwscanf page in the POSIX Programmer's Manual 💖. Grab a boba, we're doing wide-character formatted input today.

✨ PROLOG ✨

so like, important heads up first: 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, iykyk), or honestly the interface may not be implemented on Linux at all 😭. vibe check accordingly.

💅 NAME 💅

vfwscanf, vswscanf, vwscanf — wide-character formatted input of a stdarg argument list 🎀

🦋 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);

👑 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 (not me starting drama, fr). This volume of POSIX.1‐2017 defers to the ISO C standard.

ok so here's the tea ☕: vfwscanf(), vswscanf(), and vwscanf() shall be equivalent to fwscanf(), swscanf(), and wscanf() respectively — the only glow-up is that instead of being called with a variable number of arguments, they're called with an argument list as defined in the <stdarg.h> header. That's it, that's the whole flex.

⚠️ These functions shall not invoke the va_end macro. And because these functions invoke the va_arg macro, the value of ap after the return is unspecified 💀 — so don't go poking at it afterwards and expecting answers.

🌈 RETURN VALUE 🌈

Refer to fwscanf(). (go read that page bestie, it's all there 💜)

🙈 ERRORS 🙈

Refer to fwscanf().

The following sections are informative.

🍓 EXAMPLES 🍓

None. 😌 a peaceful, example-free existence.

🧚 APPLICATION USAGE 🧚

Applications using these functions should call va_end(ap) afterwards to clean up 🫶. yes bestie, clean up after yourself, it's giving basic hygiene.

💀 RATIONALE 💀

None.

⭐ FUTURE DIRECTIONS ⭐

None.

🔥 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 .

ok that's the whole page, you ate that 🎀 mwah 💋

sign-off szn: this icon of a document is brought to you by IEEE/The Open Group, dated 2017, and it lives under the name VFWSCANF(3POSIX) — periodt. 💅✨

📦 where this page comes from