SUMMARY A*B^C+X*Y^Z doesn't yield the correct result. (A*B^C)+(X*Y^Z) does. STEPS TO REPRODUCE 1. Open KCalc in science mode; 2. paste `5×3^3+2×3^2` in the input field and press the "Return" key. OBSERVED RESULT KCalc shows "225". EXPECTED RESULT We expect the same result as the one yielded by `(5×3^3)+(2×3^2)`, i.e. "153". SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 40 KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.8.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Another example: `7×4^5+5×3^4` (yields "10003") and `(7×4^5)+(5×3^4)` (yields "7573").
I apologize if I overstated the severity of the bug, but that seemed quite important to me. I'm assuming the admins have the option to downgrade it if they judge it excessive...
Sorry for not having been able to figure this out early enough to put it in the description, but it seems like `5×3^3+2×3^2` is parsed as `5×(3^3+2×3^2)`. Similarly, `7×4^5+5×3^4` yields the same result as `7×(4^5+5×3^4)`.
Can confirm
A possibly relevant merge request was started @ https://invent.kde.org/utilities/kcalc/-/merge_requests/165
My bad, thanks for the heads up, try reinstalling the latest.
(In reply to Gabriel Barrantes from comment #5) > My bad, thanks for the heads up, try reinstalling the latest. You are very much welcome for the heads up. Thank *you* for the fix. Not sure what you mean by "try reinstalling the latest", though. I don't see why my testing would be more valuable than yours, so I'm wildly guessing that you're not asking me to check is everything is fine on my side of things... Are you suggesting that I upgrade to version 24.11 to have the fix take effect? I'm new to this, so I don't really know to which version(s) your commit will be applied, or when the package will be updated in the repo, or what I'm supposed to do at this point, really.
> what I'm supposed to do at this point, really. I meant try to update so you can get the fixed version. To be honest I not quite sure how long would take to propagate, it depends on what repository your distro is using. Either way should be fixed in nex release. Either way, thanks for the bug report, is really hard to cover all edge cases and is good to have it tested.
(In reply to Gabriel Barrantes from comment #7) > I meant try to update so you can get the fixed version. > quite sure how long would take to propagate, it depends on what repository > your distro is using. Either way should be fixed in nex release. Alright! Cheers! > Either way, thanks for the bug report, is really hard to cover all edge > cases and is good to have it tested. No problem. You guys do a lot of great work, so it's the least I can do.
*** Bug 497580 has been marked as a duplicate of this bug. ***