4 ms·
There's a reason "bug for bug compatibility" is a thing, but this isn't it. I highly doubt anyone is relying on this, because it's completely stupid behavior.
by actually_a_dog 5y ago
There's a reason "bug for bug compatibility" is a thing, but this isn't it. I highly doubt anyone is relying on this, because it's completely stupid behavior.
- my123 5y agoRelying on completely insane behavior is a thing that surprisingly, lots of programs do...
- daniel-thompson 5y ago> I highly doubt anyone is relying on this, because it's completely stupid behavior. 1. The person who posted the SO question said they rely on it. There are probably more who haven't discovered they're affected by this or who haven't spoken up yet. 2. An average VBA developer might be more likely to do something like this than you would be.
- actually_a_dog 5y agoI just re-read the whole page, and, no, the SO poster is not relying on it. And, if anyone is relying on a bug that makes an if condition go the wrong way, that's so monumentally stupid, they deserve to have their stuff break.
- daniel-thompson 5y agoFrom the original question: > and also it blocks a migration to Office 64 here, because we can not get our code out
- malf 5y agoWrong direction.
- magpi3 5y agohttps://xkcd.com/1172/ https://xkcd.com/1172/ That noted, a broken IF statement does seem like a very serious compiler bug. And especially since the correct behavior occurs on Macs, I think a fix is necessary. The language should be consistent across all platforms at the very least.
- yegle 5y agohttps://www.hyrumslaw.com/ https://www.hyrumslaw.com/