Get the latest tech news
Every bug/quirk of the Windows resource compiler (rc.exe), probably
Fuzz testing decades-old software can turn up some curious behaviors
Executable icons that show up in Explorer Version information that integrates with the Properties window Defining dialogs/menus that can be loaded at runtime Localization strings Embedding arbitrary data etc. So, somehow, the subtraction of the zero caused the BEGIN expected in dialog error, and then the Windows RC compiler immediately restarted its parser state and began parsing a new resource definition from scratch. While it would make sense for these strings to be used to populate the initial options in the combo box, I couldn't actually get modifications to the DLGINIT to affect anything in the compiled program in my testing.
Or read this on Hacker News
