Re:How can I get this 8 year old VBA 64-bit compiler bug fixed?
by adrianmonk on Sunday August 15, 2021 @11:49AM
(#28189716)
Fix or don't fix aren't the only two options. The third option is to provide a fix that can be enabled or disabled by compiler users as needed.
For maximum backward compatibility, the fix could be disabled by default. But enabling by default still provides a path to backward compatibility with a small amount of manual work for those who need it.
For those who don't want the broken behavior, it might be a hassle to have to enable the fix, but that's still much better than not having a fix and having to write crazy code as a workaround.
For maximum backward compatibility, the fix could be disabled by default. But enabling by default still provides a path to backward compatibility with a small amount of manual work for those who need it.
For those who don't want the broken behavior, it might be a hassle to have to enable the fix, but that's still much better than not having a fix and having to write crazy code as a workaround.
I don't know VBA, but as a guess, the #Const directive (https://docs.microsoft.com/en-us/office/vba/language/referen...) for compile-time constants looks like it could be a reasonable way to implement a switchable compiler fix.