[kcalc] [Bug 447347] pasting numbers starting with zero are parsed as octal

2024-01-26 Thread Matteo Croce
https://bugs.kde.org/show_bug.cgi?id=447347 --- Comment #10 from Matteo Croce --- Hi, where the cited attachments can be found? -- You are receiving this mail because: You are watching all bug changes.

[kcalc] [Bug 447347] pasting numbers starting with zero are parsed as octal

2024-01-25 Thread Carl Schwan
https://bugs.kde.org/show_bug.cgi?id=447347 Carl Schwan changed: What|Removed |Added Latest Commit||https://invent.kde.org/util |

[kcalc] [Bug 447347] pasting numbers starting with zero are parsed as octal

2023-11-09 Thread Gabriel Barrantes
https://bugs.kde.org/show_bug.cgi?id=447347 Gabriel Barrantes changed: What|Removed |Added Status|ASSIGNED|CONFIRMED -- You are receiving this mail b

[kcalc] [Bug 447347] pasting numbers starting with zero are parsed as octal

2023-11-08 Thread Gabriel Barrantes
https://bugs.kde.org/show_bug.cgi?id=447347 Gabriel Barrantes changed: What|Removed |Added CC||radius.soukr...@gmail.com --- Comment #8 fr

[kcalc] [Bug 447347] pasting numbers starting with zero are parsed as octal

2023-11-08 Thread Gabriel Barrantes
https://bugs.kde.org/show_bug.cgi?id=447347 Gabriel Barrantes changed: What|Removed |Added CC||u...@compsci.cas.vanderbilt

[kcalc] [Bug 447347] pasting numbers starting with zero are parsed as octal

2023-11-02 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=447347 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED

[kcalc] [Bug 447347] pasting numbers starting with zero are parsed as octal

2023-10-30 Thread Gabriel Barrantes
https://bugs.kde.org/show_bug.cgi?id=447347 Gabriel Barrantes changed: What|Removed |Added Assignee|ete...@alum.rit.edu |gabriel.barrantes.dev@outlo

[kcalc] [Bug 447347] pasting numbers starting with zero are parsed as octal

2022-01-13 Thread Matteo Croce
https://bugs.kde.org/show_bug.cgi?id=447347 --- Comment #4 from Matteo Croce --- The problem is that the issue is very silet. An user can paste "01234" in kcalc and the calculations will be wrong without noticing. That's what happened to me, I pasted an hex offset, something like 0123 and it

[kcalc] [Bug 447347] pasting numbers starting with zero are parsed as octal

2022-01-13 Thread Evan Teran
https://bugs.kde.org/show_bug.cgi?id=447347 --- Comment #3 from Evan Teran --- Understood, unfortunately the convention for octal numbers is "starts with a 0". Admittedly, this is considered confusing to many, so much so that python added 0o1234 as an alternative octal prefix. Perhaps kcalc could

[kcalc] [Bug 447347] pasting numbers starting with zero are parsed as octal

2022-01-13 Thread Matteo Croce
https://bugs.kde.org/show_bug.cgi?id=447347 --- Comment #2 from Matteo Croce --- Yes, that's ok with the "0x" prefix, because 0x1234 is undoubtedly an hex value, but is very, very common to have hex or decimal numbers starting with 0. -- You are receiving this mail because: You are watching all

[kcalc] [Bug 447347] pasting numbers starting with zero are parsed as octal

2022-01-13 Thread Evan Teran
https://bugs.kde.org/show_bug.cgi?id=447347 --- Comment #1 from Evan Teran --- Yeah, this is a long standing thing where there's two camps. Some people people want the input data's apparent base to be respected. So pasting in `0x1234` will past in a hex value, even if you're in decimal mode Som