Oh right, I misread. And yeah not sure (my win32 repro targets have all been locked for a while) but with all the facepalm regressions I’ve read about lately it really could be anything.
From my experience, the number one culprit of legacy code breaking is someone asking if anyone knows how it works. Second most common culprit is someone making a “quick patch” to legacy code.
Oh right, I misread. And yeah not sure (my win32 repro targets have all been locked for a while) but with all the facepalm regressions I’ve read about lately it really could be anything.
From my experience, the number one culprit of legacy code breaking is someone asking if anyone knows how it works. Second most common culprit is someone making a “quick patch” to legacy code.
lol damn, flinched at both even though I was prepared