https://bugs.kde.org/show_bug.cgi?id=468605
--- Comment #8 from Igor Kushnir <igor...@gmail.com> --- (In reply to Alessandro Carinelli from comment #5) > I had an idea: after we get trimmedText we move backwards starting from the > character right before the '.' checking every character until we find > something different from a letter (upper or lowercase), an underscore or a > digit, in this way we should find the first character in the identifier or > literal that precedes the '.', if such first character is a digit we know > that we are dealing with a floating point literal and skip the substitution. > I tried it and it seems to work without noticeable performance issues. This proposed workaround is too narrow for my liking. What if the user types a name of a constant of a built-in type instead of an integer literal? But I guess if there is no more general fix that is acceptable, this workaround might do. -- You are receiving this mail because: You are watching all bug changes.
