winsdk-10

> Is this something you have to sign an NDA with Microsoft to get access to the headers and docs for it? Or will I find the headers hidden away in the WDK somewhere? Turns out the header file is included in the Windows 10 SDK, as km/nthalext.h Not the very latest version, but someone posted it on GitHub here: https://github.com/tpn/winsdk-10/blob/master/Include/10.0.16... (You can download the multi-gigabyte Windows 10/11/2022 SDKs to get a more recent one, although not sure if anything has changed.) Still doesn't seem to be any public documentation. The header includes very detailed comments, but (as you'd expect for header file comments) they concentrate on the nitty-gritty and omit the big picture. Searching "nthalext.h" on GitHub finds source code for a handful of HAL extensions, so at least there is some sample code to look at. Micro

I think that the author hasn't checked them all. Even this isn't checking them all. The MUSL C library' sscanf() does not do this, but does call memchr() on limited substrings of the input string as it refills its input buffer, so it's not entirely free of this behaviour. * https://git.musl-libc.org/cgit/musl/tree/src/stdio/vsscanf.c The sscanf() in Microsoft's C library does this because it all passes through a __stdio_common_vsscanf() function which uses length-counted rather than NUL-terminated strings internally. * https://github.com/tpn/winsdk-10/blob/master/Include/10.0.16... * https://github.com/huangqinjin/ucrt/blob/master/inc/corecrt_... The GNU C library does something similar, using a FILE structure alongside a special "operations" table, with a _rawmemchr() in the initialization. * https://github.com/bminor/glibc/blob/master/