https://bugs.kde.org/show_bug.cgi?id=469079
--- Comment #5 from Eugene Shalygin <eugene.shalygin+bugzilla....@gmail.com> --- (In reply to Igor Kushnir from comment #4) > The failing KDevelop's tests use a default standard and C++14, so the issue > isn't limited to C++20. Does the standard version make a difference in your > case? Yes, definitely. Everything works fine in the C++17 mode. > What do you typedef these types to? float, double, and __float128. > I agree that injecting type aliases would be safer than macros. Do you mean > this option > https://clang.llvm.org/docs/ClangCommandLineReference.html#cmdoption-clang- > include-file ? Yes, the force-include option. > Does the Clang version make a difference or only GCC's? If only GCC's, then > I think the header should be included `if (isCpp)`, similarly to > https://invent.kde.org/kdevelop/kdevelop/-/commit/ > 35ea746ddd49e872998152cc157152c2cb5b86ea . I haven't tried clang-15, but why would it work if the newer version still has no these types? https://gcc.gnu.org/onlinedocs/gcc/Floating-Types.html says they are a new addition in C. > The header file can be installed with KDevelop, but then the exact path to > the installed header would have to be found at run-time... Alternatively the > header file can be stored in resources and copied into a temporary file at > run-time (similarly to how the define files are stored in /tmp/kdevelop.*). I see no big difference from the user point of view, and I guess it is not a big deal to find out own installation prefix at run-time? -- You are receiving this mail because: You are watching all bug changes.
