I don’t know what this image is supposed to tell us, but I can confirm that KCalc behaves badly in some common situations. (At least, it does in Plasma 5.) Want to see an example?
Put it in Simple Mode, and try copying and pasting various multi-digit numbers with leading zeroes. Some of them work fine. Others, like 054 and 009, yield surprising results.
Spoiler:
054 becomes 044
009 becomes nan
A programmer or mathematician might be able to deduce that KCalc is trying to interpret those numbers as octal (base 8 instead of base 10), assuming they’re paying close attention. That doesn’t help anyone who is just trying to total a bunch of values from a document, using their default desktop calculator, and doesn’t notice a misinterpreted value along the way. Their total will just be wrong, or in the case of nan, they will just be frustrated that the calculator doesn’t work.
This behavior is probably not appropriate for Simple Mode.
Curiously, it does the same thing even in Numerical System Mode with decimal (base 10) explicitly selected, which is absolutely not appropriate.
I don’t know what this image is supposed to tell us, but I can confirm that KCalc behaves badly in some common situations. (At least, it does in Plasma 5.) Want to see an example?
Put it in Simple Mode, and try copying and pasting various multi-digit numbers with leading zeroes. Some of them work fine. Others, like 054 and 009, yield surprising results.
Spoiler:
054 becomes 044
009 becomes
nanA programmer or mathematician might be able to deduce that KCalc is trying to interpret those numbers as octal (base 8 instead of base 10), assuming they’re paying close attention. That doesn’t help anyone who is just trying to total a bunch of values from a document, using their default desktop calculator, and doesn’t notice a misinterpreted value along the way. Their total will just be wrong, or in the case of
nan, they will just be frustrated that the calculator doesn’t work.This behavior is probably not appropriate for Simple Mode.
Curiously, it does the same thing even in Numerical System Mode with decimal (base 10) explicitly selected, which is absolutely not appropriate.
@mox wow that’s even worse than losing continuity for the sakes of that new history feature (using Kcalc version 24.05.0)
here’s what I did before getting the input error:
2*2 [enter]
*2 [enter]
I was expecting to read “8” but got “input error” instead
I followed your steps and got 8 in KCalc 22.12.3.
Perhaps you found a bug in your version? You can search for existing bug reports, or create new ones, here: https://bugs.kde.org/
@mox
https://bugs.kde.org/show_bug.cgi?id=487566#c3