This just isn't really something that can be cleanly abstracted to do what you want it to do, even if you can make the code "look" the same.
But again, it looks like a nice, clean, modern C++ library. Just IMHO misapplied.
This just isn't really something that can be cleanly abstracted to do what you want it to do, even if you can make the code "look" the same.
But again, it looks like a nice, clean, modern C++ library. Just IMHO misapplied.
It's not that uncommon. Even notepad uses it:
https://blogs.msdn.microsoft.com/oldnewthing/20180521-00/?p=...
Just a data point, but we use memory mapping (both with and without names) in our product that runs on Windows.
Unheared by you.
In a world consumed by Electron apps and Javascript, lots of people couldn't care any less about performant IPC, sharing data across processes, and multiprocessing in general.
Really? Most larger (Windows) codebases I know of use memory mapping.
This must be incorrect.
Jeffrey Richter's advanced windows, a very widespread win32 book, introduced this technique to a LOT of developers, just when windows was the hot stuff for programmers. I don't think I've seen a win32 code base >100 Kloc without mapping. Understanding and using it is one of those rites of passage that marks the switch from junior to medior win32 developer.