f35 kdevelop 5.6.2 :: within project sting_view not found in std?

[René J.V. Bertin]

On Friday February 11 2022 14:15:14 Adrian Sevcenco wrote:

>and that std=c++11 is just wrong...
>any idea how can i instruct the clang parser to used c++17?

The prefs tab where you select the dialect to use also has a text entry for setting custom arguments passed to the parser. Normally that is inactive (text greyed out) and should use the value from the dialect selector, but it probably doesn't if it somehow got modified manually into a custom set of arguments. And it's not impossible that this happens when you just click in the entry field. Either way, you can set the appropriate std argument there.

I suppose that removing the project from your session only limited the amount of output spilled on your terminal, right? KDevelop doesn't use cross-project parsing information.
Suggestion: turn off the automatic full-project parsing on load/startup (in the global settings). That way only the files you open get parsed (+ their headers) which saves time and RAM (potentially a lot of both). Plus parsing output on the terminal, if you activate that.

R.