6 ms·
Windows Implementation Libraries: type-safe C++ interfaces for Windows patterns
- TillE 8y agoOh wow, this is exactly what I've always wanted in my many many years of developing Windows software in C++. Despite a million fancy new API layers in newer versions of Windows, Win32 is very much not dead, but it's still a C interface with a lot of clunky and inconsistent nonsense. This looks like the ideal modern C++ wrapper for all that.
- stinos 8y agoIt looks pretty usable indeed, I just wish they had insludes std::error_code implementations for everything. Last time I checked, getting proper error_codes (i.e. which can be compared against standard categories and which have good error description strings) for everything in the API was still some manual work.
- aninteger 8y agoIt's not too hard. Just write a simple wrapper around FormatMessage: DWORD errorCode = GetLastError(); DWORD dwFlg = FORMAT_MESSAGE_ALLOCATE_BUFFER | FORMAT_MESSAGE_FROM_SYSTEM | FORMAT_MESSAGE_IGNORE_INSERTS; LPTSTR lpMsgBuf = NULL; FormatMessageA(dwFlg, 0, errorCode, 0, (LPTSTR)&lpMsgBuf, 0, NULL); // Error message is in lpMsgBuf so make sure to free afterwards. LocalFree(lpMsgBuf);
- ksherlock 8y agoIt's even easier since the MSVC STL std::error_code (std::system_category) already does that.
- jchw 8y agoHere’s what I don’t get. Microsoft has been shipping a C++ compiler for decades, and for the most part it is the preferred language for Windows development even today. Moreover, there have been PLENTY of libraries designed to make it easier, like MFC, ATL, etc. Why didn’t this already exist?! Like I realize some of it is modern C++ and maybe Microsoft was not focusing on desktop when C++ had these innovations. But why not smart pointers for handles, error handling macros, etc. Crazy. Lateness aside, I still occasionally do write win32 stuff, usually to extend/compliment/hack upon existing win32 stuff. So this is probably going to become a goto library now, if its as good as it sounds.
- pjc50 8y ago> Like I realize some of it is modern C++ and maybe Microsoft was not focusing on desktop when C++ had these innovations This is basically it, I think; COM and HANDLEs predate working standardised C++ compilers. MFC provides higher-level abstractions. Then everyone got distracted by managed runtimes. Finally C++ has a mostly-sane framework for universal usage of smart pointers, so this is bringing them back to the old Win32 era. Unfortunately we can't get rid of wstring, but we can provide yet another layer of wrappers for it.
- cjfd 8y agoThis is a bit strange to me. It has been possible to write refcounted pointers in C++ since ages. And everybody has them in their own private library. Of Course, this introduces compatibility issues because everyone's smart pointer is different, so it is really nice that it eventually ended up in the standard library. However, it seems really hard to argue that it only now is possible to use smart points.
- nikbackm 8y agostd::unique_ptr was made possible first in C++11 thanks to move semantics. Same goes for the similar smart pointers in wil.
- munchbunny 8y agoAs the other response mentions, a lot of the win32 stuff predates C++11/0x. Also, a lot of the win32 stuff are C API's by design, not C++. If your question was "why wasn't a C++ wrapper released sooner?" I think the answer is ".NET". If your question was "why didn't the API's have C++ semantics?" I think the answer is "because a lot of it is C, not C++."
- MaxBarraclough 8y agoMicrosoft provides the 'CComPtr' class template, a ref-counting smart-pointer for COM. It's been around since very roughly the year 2000 [0] [1]. Boost's smart pointers have apparently [2] been around for about as long. If people have been rolling their own smart pointers since that time, isn't that their own fault? [0] https://docs.microsoft.com/en-us/cpp/atl/reference/ccomptr-class https://docs.microsoft.com/en-us/cpp/atl/reference/ccomptr-c... [1] https://en.wikipedia.org/wiki/Active_Template_Library#History https://en.wikipedia.org/wiki/Active_Template_Library#Histor... [2] https://www.boost.org/doc/libs/1_31_0/libs/smart_ptr/smart_ptr.htm https://www.boost.org/doc/libs/1_31_0/libs/smart_ptr/smart_p...
- zmodem 8y ago> If you are doing any non-trivial work, also be sure to have a recent version of Clang installed. Nice to see Clang being put to good use on Windows.
- sorenjan 8y agoBut why do you need two compilers?
- jhasse 8y agoMicrosoft tried to lock developers in with MSVC, but it didn't work. Now we have to wait for it to die, so that we can use Clang instead.
- doublerebel 8y agoClang and CMake are becoming first class citizens now in the Windows ecosystem. New Windows open source projects are being shipped with CMake build as default and Clang compatibility.
- dmytroi 8y agoThis is quite nice! I like the error handler monitor thing. Also quite amazing that they placed whole platform-independent (sort of) thread local storage implementation there.
- lenkite 8y agoAlso check out C++/WinRT - a _pure_ C++17 library facade over WinRT/UWP API's. https://docs.microsoft.com/en-us/windows/uwp/cpp-and-winrt-apis/intro-to-using-cpp-with-winrt https://docs.microsoft.com/en-us/windows/uwp/cpp-and-winrt-a...
- doublerebel 8y agoWinRT + coroutines makes modern Windows programming _amazing_ to write and read, and efficient to run. This plus the xlang (compiler? toolset?) system, all open-sourced, shows how Microsoft has hedged against whichever platform will win the next round. Kenny Kerr deserves much credit for pushing all of C++ forward with these concepts.