Bug 372923

Summary: wrong language parser arguments aren't pointed out
Product: [Applications] kdevelop Reporter: OlafLostViking <olaf.the.lost.viking>
Component: Language Support: CPP (Clang-based)Assignee: kdevelop-bugs-null
Status: CONFIRMED ---    
Severity: minor Keywords: junior-jobs
Priority: NOR    
Version First Reported In: 5.0.2   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description OlafLostViking 2016-11-25 17:14:19 UTC 
It's great that I can change the parser arguments in "Configure Language Support"! But when I give a wrong one, KDevelop doesn't tell me about that but parses the code wrongly. It would be better, if KDevelop mentions problems with the command line arguments that aren't accepted by the underlying libclang.

Example:
I wanted to use some C++17 features and since this is not selectable in the Profile dropdown, I added -std=c++17 to the arguments. But clang only accepts -std=c++1z for now instead, which means not even C++11/14 is parsed anymore.
Comment 1 Kevin Funk 2016-11-27 10:30:00 UTC 
+1. We should probably validate the command-line arguments & show hints in the config dialog.

Marking as junior job.