How can I get this 8 year old VBA 64-bit compiler bug fixed?

A common complaint about FOSS development or requirements is that you get what you pay for in terms of support. It&#x27;s good to see that commercial offerings are not much better!<p>MS office is arguably the biggest piece of commercial software on the planet, and as this neatly shows, you still get bugger all in terms of support. I really dislike the embedded VBA &quot;enterprise&quot; Windows&#x2F;Office world -- it either works, or you can hack it to work (CF the SO answers) or, if neither of those things are true, you are SOL...

Easiest way to get it fixed is to make it exploitable somehow. Could be an interesting VBA sandbox escape if the stack frames are incorrect

(Tangential) Got to scratch my head at this &quot;authoritatively voiced&quot; bit of advice in the SO thread:<p>&gt; Testing the result of a constructor in any language is probably a dodgy practice. It&#x27;s an object or it&#x27;s a &#x27;null&#x27;.<p>Ah, if there&#x27;s an OO language anywhere that can return null from a constructor invocation, I have yet to see it.

Some interesting points there about User voice being head d for the scrap heap (as if it was ever really given much attention from teams at MS anyway) and that VBA isn’t the focus for programmatic extension anymore.<p>Seems that the closest is the recently announced Python for Excel only (and even then I remember it seemed to be online only or something equally crippled) or PowerApps which I guess might actually be a reasonable but still online only alternative.

The bug has been in the wild for 8 years, so there are almost certainly customers who have VBA scripts that rely on that behavior. Microsoft puts a lot of emphasis on backward compatibility (or at least they used to), so I think there will be some internal debate on whether fixing the bug is more or less disruptive than just leaving it in.

Use it to demonstrate an exploit.

This is the kind of bug that open-source people love to work on. But, are people experiencing it in the wild? If so, Microsoft will fix it. If not, enjoy the other things Microsoft spent their time on otherwise and forget about it.

Shrug... so there&#x27;s an 8 year old VBA bug? I&#x27;m sure there are old Windows&#x2F;IOS&#x2F;Android&#x2F;MacOS&#x2F;Ubuntu bugs that similarly have not been fixed.<p>Here&#x27;s a 6 year old IOS bug that affects my old videos that&#x27;s still around, despite being reported when it first cropped up: <a href="https:&#x2F;&#x2F;discussions.apple.com&#x2F;thread&#x2F;7226531" rel="nofollow">https:&#x2F;&#x2F;discussions.apple.com&#x2F;thread&#x2F;7226531</a><p>Not sure why the article is HN newsworthy.... is the implication that because this is a &quot;developer tooling&quot; bug, it&#x27;s somehow more important, or more likely to be fixed, than any other bug? IMHO, that&#x27;s not a valid expectation.