3 ms·
Reading the messages on this bug shows you how much of a hunt it was. It turned out to be undocumented messaging behavior in user32.
by Hydraulix989 11y ago
Reading the messages on this bug shows you how much of a hunt it was. It turned out to be undocumented messaging behavior in user32.
- davidgerard 11y agoThe Win32 documentation is sometimes best treated as historical fiction with an unreliable narrator. This is why Wine has a massive suite of test cases.
- Hydraulix989 11y agoThat's a clever way of perpetuating vendor lock-in: write shitty documentation that is still helpful for application developers but also simultaneously makes life VERY hard for interop layer developers (like the WINE project).
- lolo_ 11y agoAnd given MS's business practices in the past (seem a very different company these days) it's actually pretty believable at least some of this was on purpose. Certainly when you take into account all the undocumented API functions used by office et al.
- lolo_ 11y agoPerhaps Microsoft's recent move towards open source might might thinks easier - as far as I can tell there are far too many copyright issues with the _entirety_ of the windows source code for a complete open sourcing there, but they could perhaps open up core parts of the codebase. Imagine Microsoft engineers contributing to wine also. Perhaps I am dreaming :)
- Hydraulix989 11y agoI call it "calculated altruism." :)