musl/src/stdio/swscanf.c

#include <stdarg.h>
#include <wchar.h>
#include "libc.h"

int swscanf(const wchar_t *restrict s, const wchar_t *restrict fmt, ...)
{
	int ret;
	va_list ap;
	va_start(ap, fmt);
	ret = vswscanf(s, fmt, ap);
	va_end(ap);
	return ret;
}

weak_alias(swscanf,__isoc99_swscanf);
initial check-in, version 0.5.0 2011-02-12 00:22:29 -05:00			`#include <stdarg.h>`
			`#include <wchar.h>`
Add ABI compatability aliases. GNU used several extensions that were incompatible with C99 and POSIX, so they used alternate names for the standard functions. The result is that we need these to run standards-conformant programs that were linked with glibc. 2013-04-05 23:20:28 -07:00			`#include "libc.h"`
initial check-in, version 0.5.0 2011-02-12 00:22:29 -05:00
use restrict everywhere it's required by c99 and/or posix 2008 to deal with the fact that the public headers may be used with pre-c99 compilers, __restrict is used in place of restrict, and defined appropriately for any supported compiler. we also avoid the form [restrict] since older versions of gcc rejected it due to a bug in the original c99 standard, and instead use the form *restrict. 2012-09-06 22:44:55 -04:00			`int swscanf(const wchar_t restrict s, const wchar_t restrict fmt, ...)`
initial check-in, version 0.5.0 2011-02-12 00:22:29 -05:00			`{`
			`int ret;`
			`va_list ap;`
			`va_start(ap, fmt);`
			`ret = vswscanf(s, fmt, ap);`
			`va_end(ap);`
			`return ret;`
			`}`
Add ABI compatability aliases. GNU used several extensions that were incompatible with C99 and POSIX, so they used alternate names for the standard functions. The result is that we need these to run standards-conformant programs that were linked with glibc. 2013-04-05 23:20:28 -07:00
			`weak_alias(swscanf,__isoc99_swscanf);`