Calculator app still can't do e^x with negative arg

After 10 months (at least) the calculator.app bug still exists: can't use e^x with a negative number.


Weirdly, the result depends on whether you are in RPN or "normal" mode. In RPN mode you get "Not a number" while in "normal" mode you get 0 (though on my other, nearly-identical MBP, I get 8?!!!).


Super pathetic.

Posted on Sep 21, 2018 7:37 AM

Reply
13 replies

Sep 21, 2018 8:48 AM in response to Luis Sequeira1

Yes, I opened a support case.


To everyone with workaround suggestions: Yes, I know. I took math in middle school. I know there are other apps, my iPhone, and I could work it out using the series expansion.


The point is that this is an onerous, obvious, and easy bug to fix, particularly for a trillion-dollar company. Particularly since it's been known for at least 10 months.


It makes one wonder what other non-obvious -- but possibly more onerous -- bugs may exist that are also being ignored.

Oct 12, 2018 12:04 PM in response to BobTheFisherman

Bob, thanks for pointing out the obvious workaround. But I agree with others that there shouldn't have to be a workaround - should take a trivial effort to fix and just an embarrassment to leave it broken for so long. And it works ok on iOS, but not MacOSX - go figure. Further, 10^(negative number) works, so why not with e? And even further, if this is the importance Apple gives to a simple calculator, how do we know to trust whatever other answers the Calculator app gives? If I were at school learning logs and powers, I might accept ln(-1) gives "Not a number" (which is correct) and then believe that e^-1 also has no answer because the Mac Calculator app says so. Unbelievable.

Sep 27, 2018 9:01 AM in response to BobTheFisherman

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.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Calculator app still can't do e^x with negative arg

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.