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 bac

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. I don't know VBA, but as a guess, the #Const directive (https://docs.microsoft.com/en-us/office/vba/language/reference/user-interface-help/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.