Bob (not your real name probably),
Thanks for the info but, as noted earlier on the thread, I'm well aware of all the workarounds and computational options.
This thread is about the fact that the calculator is broken. And that Apple hasn't fixed it in over 10 months (and it's still broken in Mojave). Which, to me, says more about Apple's (lack of) interest in quality than anything else. If this onerous bug can get through the QA process (and then languishes without getting fixed), what does that say about their approach to the (undoubtedly many) other bugs that must exist in the code base that so many of us rely upon.
I also find it pretty disheartening that so many people are willing to put up with this sort of issue and discover workarounds instead. I realize that the expedient thing is to just silently move on and use something that works, but that approach will only reinforce a spiraling decline in the quality of the products we use.