Cursed C++: reinterpret_cast (yes, all of it)
For a standard feature, it’s staggeringly easy to misuse and cause undefined behavior. So what does the standard guarantee it really can do?
Game Programmer
For a standard feature, it’s staggeringly easy to misuse and cause undefined behavior. So what does the standard guarantee it really can do?
In this deep dive: How do cross-DLL function calls work, what do dllimport and dllexport do under the hood, and why does my compiler keep producing .libs next to my .dlls?
Ever needed to use some obscure library function only for it to be private?
Meet public_cast, an abomination unto good code that can see almost everything. Did I mention it’s entirely compliant with the C++ standard?
In this deep dive: CPU architecture basics, predicting function outcomes without calling them, and intercepting malloc.
The most fundamental problem of unloading and reloading code is that it can move–its contents, or the entire image. In this deep dive: vptrs, compiler design, and deducing object memory layouts.
A proof-of-concept framework centered on plugins and seamless hot-reloading, with an extensive reflection and type erasure system.