Too many requirements, some of which bring us full circle. The post Why didn’t we use <CODE>Ro­Register­For­Apartment­Shutdown</CODE> to clean up the unmarshalable delegate? appeared first on The Old New Thing.

PowerPoint presentation jargon. The post Microspeak: Drain the slide, back-up slides appeared first on The Old New Thing.

An interrupt is not a fault. The post Why do we need <CODE>ud2</CODE> when <CODE>int 6</CODE> is right there? appeared first on The Old New Thing.

Getting the results back out. The post C++ futures part 5: <CODE>std::<WBR>future</CODE> and <CODE>std::<WBR>shared_future</CODE> appeared first on The Old New Thing.

Providing the case that the C++ language won't do. The post C++ futures part 4: What if I want an immediate on-thread <CODE>std::async</CODE>? appeared first on The Old New Thing.

Doing things later in different ways. The post C++ futures part 3: The mental model for <CODE>std::async</CODE> appeared first on The Old New Thing.

Building things out of the state. The post C++ futures part 2: The mental model for <CODE>std::promise</CODE>, <CODE>std::packaged_task</CODE> appeared first on The Old New Thing.

Managing a value that is produced later. The post C++ futures part 1: The mental model appeared first on The Old New Thing.

Mapping them to concepts from C# and the now-defunct C++/CX. The post One way of thinking about access specifiers in C++/WinRT implementation types appeared first on The Old New Thing.

Not always. The post If one anti-malware software is good, does that make two better? appeared first on The Old New Thing.

They weren't defined, not even as undefined. The post How can undefined opcodes <CODE>ud0</CODE> and <CODE>ud1</CODE> have parameters? How undefined were they? appeared first on The Old New Thing.

It shouldn't execute, but for different reasons. The post Why does the compiler sometimes use <CODE>ud2</CODE> and sometimes <CODE>int 3</CODE> for code that shouldn’t execute? appeared first on The Old New Thing.

Hot-patching is for Windows, not for you. The post If somebody tries to hot-patch an already-hot-patched function, how do they avoid conflicts? appeared first on The Old New Thing.

They either predate hot-patching or never needed it. The post Why is there no Windows hot-patching support for other architectures like 32-bit ARM and MIPS? appeared first on The Old New Thing.

Once again, the benefit of fixed-length instructions. The post Windows on Itanium also provided for hot-patching, in an even simpler way appeared first on The Old New Thing.

Fixed-length instructions makes it a much easier task. The post Windows on AArch64 also provides for hot-patching, but it’s much simpler than on x86 appeared first on The Old New Thing.

Swearing is also poor form. The post As a general rule, calling product support while drunk is not recommended appeared first on The Old New Thing.

Only on first execution. The post C++ reminder: Function-local static variables are initialized only once, even if it looks like they get initialized multiple times appeared first on The Old New Thing.

Trying to figure out what the interloper was trying to. The post Debugging walkthrough: Access violation on nonsense instruction, episode 3 appeared first on The Old New Thing.

Another example to add to the list. The post No, really, you need to pass all unhandled messages to DefWindowProc, part 2 appeared first on The Old New Thing.

Let the library do the math for you. The post When working with Win32 <CODE>FILETIME</CODE>, don’t forget that you have <CODE>std::chrono</CODE> now appeared first on The Old New Thing.

Right-clicking and shift-clicking. The post A brief history of Windows scroll bar shortcuts appeared first on The Old New Thing.

Being wary of how people use it and how it interacts with other types. The post What’s the highest legal <CODE>FILETIME</CODE>? Is it safe to use? appeared first on The Old New Thing.

Do you try again or give up? The post Comparing exception behavior of magic statics, <CODE>std::<WBR>call_<WBR>once</CODE>, and <CODE>std::<WBR>async</CODE> appeared first on The Old New Thing.

Simple vs complex machinery. The post <CODE>std::call_once</CODE> vs. <CODE>std::async</CODE> appeared first on The Old New Thing.

They sort of do the same thing, but differently. The post Magic statics vs. <CODE>std::call_once</CODE> appeared first on The Old New Thing.

It used to start at 1, but that was the old system. The post Why do Microsoft job levels start in the high 50’s instead of starting at a sane number like 1? appeared first on The Old New Thing.

Perhaps it wasn't necessary, or perhaps it didn't occur to them that this a problem. The post Why didn’t <CODE>Read­Directory­ChangesW</CODE> provide a way to correlate the two sides of a rename operation? appeared first on The Old New Thing.

Not through normal means. The post How can I remove the Close button from my window caption? appeared first on The Old New Thing.

It came after ud0 and ud1. The post Why is the x86 undefined instruction called <CODE>ud2</CODE>? Why 2? appeared first on The Old New Thing.