Windows Runtime (aka UWP) was supposed to be modern API without any of <windows.h> horrors. It has new horrors instead! For example, this code does not compile. http://aras-p.info/blog/2018/01/19/UWP/WinRT-Headers-are-Fun-not/
@aras this is why I only forward declare the platform APIs I need
https://github.com/garettbass/app/blob/master/internal/windows/api/api.inl
@garett have you done that for UWP thing too? :)
@aras I haven’t tried UWP, but I’m curious whether it is C-accessible. I was able to forward declare Cocoa and Metal APIs in C++ (no Objective-C syntax) via the C-based Objective-C runtime.
@aras IIUC, the WinRT headers you’re wrangling are C++, not C++/CX as I initially thought. Gives me some hope.
@aras I did WinRT once, never again. Awful API.
@bitshifter Agree. There's no other way to get to some stuff however (e.g. Hololens) :(
@aras @bitshifter Get someone to wrap it up and hide it from you behind another abstraction :P
@aras I saved myself all those troubles and ditched Windows 8 years ago! :)
@duckz some of us don't have such luxury :(
@aras wow - that effectively means using whatever::Plane in all code including the header - if i'm reading stackoverflow correctly (the `typdef struct X X;` thing)
- s.a. https://stackoverflow.com/questions/612328/difference-between-struct-and-typedef-struct-in-c#612350