Re:How can I get this 8 year old VBA 64-bit compiler bug fixed?
by actually_a_dog on Sunday August 15, 2021 @09:59AM
(#28188783)
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.
[ Parent
| on HN ]
Re:How can I get this 8 year old VBA 64-bit compiler bug fixed?
by my123 on Sunday August 15, 2021 @10:23AM
(#28188970)
Relying on completely insane behavior is a thing that surprisingly, lots of programs do...
Re:How can I get this 8 year old VBA 64-bit compiler bug fixed?
by magpi3 on Sunday August 15, 2021 @10:42AM
(#28189129)
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.
Re:How can I get this 8 year old VBA 64-bit compiler bug fixed?
by daniel-thompson on Sunday August 15, 2021 @10:41AM
(#28189116)
> 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.
Re:How can I get this 8 year old VBA 64-bit compiler bug fixed?
by actually_a_dog on Sunday August 15, 2021 @11:21AM
(#28189469)
I 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.
Re:How can I get this 8 year old VBA 64-bit compiler bug fixed?
by daniel-thompson on Sunday August 15, 2021 @11:52AM
(#28189737)
From the original question:
> and also it blocks a migration to Office 64 here, because we can not get our code out