proxy VS old-new-win32api

Proxy seems more likely than Dyno or AnyAny to be a standard way of doing this in C++'s future.

https://github.com/microsoft/proxy Implementation submitted for standarization

So basically you have to undo the type erasure? I think I'm going to try the proxy library found here. https://github.com/microsoft/proxy

Do you have any recommendations?

I assume this is the one you’re talking about https://devblogs.microsoft.com/oldnewthing/

I was curious, went to the end (page 699!) and it’s pretty interesting. But obviously it’s hard to find the important ones.

Not quite. DOS was just the bootloader for Windows 9x.

While Windows 95's kernel didn't have the full feature set of NT, it still was more sophisticated than DOS.

Source: https://devblogs.microsoft.com/oldnewthing/?p=24063

Some registry keys also have The Old New Thing posts by Raymond Chen [1] /s

[1] https://github.com/mity/old-new-win32api#registry

Lucky you, Raymond Chen did an overview in his blog series "Inside STL". You can view it here: https://devblogs.microsoft.com/oldnewthing/

Yes, Raymond Chen describes such fixes in [several blog posts](https://devblogs.microsoft.com/oldnewthing/) and in his book The Old New Thing. Check the old posts, back at the beginning. There are posts about to which lengths they went to ensure buggy applications still worked after an update or a fix.

https://learn.microsoft.com/en-us/archive/blogs/larryosterman/ https://learn.microsoft.com/en-us/archive/blogs/ https://devblogs.microsoft.com/oldnewthing/

A couple of blogs as an example: - Raymond Chen - https://devblogs.microsoft.com/oldnewthing/ - Pavel Yosifovich - https://scorpiosoftware.net/ - Adam Sawicki - https://asawicki.info/index - Matt Pettineo - https://therealmjp.github.io/ - Scratchapixel - https://www.scratchapixel.com/

https://devblogs.microsoft.com/oldnewthing/