Creating a fake agile wrapper that is technically agile but is not useful outside its home apartment, part 5
Cheating with std::unique_ptr.
Dev Blogs
Cheating with std::unique_ptr.
Moving things around if possible.
Forcing an object into the global interface table.
Using a reference stored in the global interface table.
Looking for a COM reference that is between strong and weak.
Maybe it doesn't matter.
Inferring the code's history.
Watching the bits disappear.
Decoding where those integer came from.
Math is hard. Let's go counting!
Rotating in the minimum number of steps by performing cycle decomposition.
Moving in a straight line, in a different way.
You need to pump messages when idle, but maybe you are never idle.
ERROR_ARENA_TRASHED error code?
The storage control blocks were destroyed.
Otherwise, it'll get mapped back down to the 8-bit code page.
You don't. All files are binary at the file system level.
scope_exit RAII type
But maybe it's not worth it.
Somehow xor became the most popular version.
Not a direct line to Bill Gates's office.
Why is this even a question?
You'll have to ask nicely.
WriteProcessMemory be made faster by avoiding the intermediate buffer?
I guess it could, but why bother?
A little trivia.
Are you even compiling the correct file?
scope_exit for running code at scope exit. C# says "We have scope_exit at home."
You can wrap it in an IDisposable.