winsdk

This project is an attempt to provide a smaller, more separated, and more standards conformant version of the Windows SDK. Some of its goals are:

• Separate functionality into separate includes, to improve build time
• Purge the use of macros (e.g. min, max, etc.) in favor of constants/inline functions
• Replace use of "Windows typedefs" with clearer, more consise types (e.g. DWORD -> std::uint32_t)
• Remove uses of SAL and hungarian
• Improve conformance, so that it builds with Clang without ms-compatability
• Rename types/constants to more "C++ friendly" snake_case names

Type mappings

Here's an (incomplete) list of the mapping between "Windows types" and their equivalent type(s) used in this project:

Windows Type	Actual Type
HANDLE	void* (or winsdk::handle_t)
BOOL	std::int32_t (or winsdk::bool_t)
WORD	std::uint16_t
DWORD	std::uint32_t
PSTR	char*
PCSTR	const char*
PWSTR	wchar_t*
PCWSTR	const wchar_t*
PVOID	void*

Namespaces

Functionality is split into two separate namespaces (and files are placed in two separate directories). Functionality that reflects the Windows SDK directly (i.e. the ABI) is placed in the winsdk directory and all contents are placed in the winsdk:: namespace. Functionality that builds off these functions are placed in the win32 directory and all contents are in the win32:: namespace. That is, the declarations for functions such as CreateFileA, CloseHandle, etc. are placed in the winsdk namespace, whereas types such as unique_handle are placed in the win32 namespace.

Linking

As mentioned above, all ABI function declarations are placed in the winsdk:: namespace. This is primarily to avoid conflicts if the actual Windows SDK headers are included somewhere (e.g. in a small subset of a project). Since these functions are declared as extern "C", their linkage will be done against the same name with the namespace removed (e.g. winsdk::CreateFileA will link against ::CreateFileA).