Version: (using Devel) OS: Linux Installed from: Compiled sources KDevelop fails to parse the following code: class A { public: void bar(); private: int baz; }; class B { public: typedef A Foo; }; void B::Foo::bar() { baz = 12; } Here, in the line "baz = 12", baz is underlined in yellow, even though it is a member variable of the A class (for which B::Foo is a typedef). This screws up KMail's configuredialog.cpp quite much.
assigning to language/cpp as it seems this is rather a duchain-related problem than a parser-related one.
> it seems this is rather a duchain-related problem than a parser-related one Oh, I wasn't aware of the distinction of parser and duchain.
(In reply to comment #2) > > it seems this is rather a duchain-related problem than a parser-related one > > Oh, I wasn't aware of the distinction of parser and duchain. Its more of a bugzilla thing, we (historically) have two separate components for c++-support-plugin and the actual c++-parser. So in cases where its clear that the parser is at fault I'm assigning things to the cpp-parser component. If its anything else (wrong highlighting, wrong interpretation of a declaration, not finding some declarations etc.) its going into the language-support: CPP component. In this case you could see in the problems report that its been the semantic highlighting that found a problem, not the C++ parser...
I tried to reproduce the bug in KDevelop 5 - it no longer valid. Probably it is necessary to close.
Hello! We are working on a new clang-based C/C++ language plugin for KDevelop 5 which supersedes the old C++ plugin in KDevelop 4. See e.g.: https://www.kdevelop.org/news/first-beta-release-kdevelop-500-available Due to a lack of manpower, we cannot fix bugs in the old C++ plugin. We rather want to supply a good Clang based C++ experience for KDevelop 5 than wasting our time on the legacy C++ support for KDevelop 4. With the new clang-based C/C++ language plugin, the bug presented here does not occur. In my testing. For these reasons, I'll close this bug. Please stay tuned for KDevelop 5. If you think this bug is applicable to Clang/KDevelop 5, please reopen the report and add new information on how to reproduce the bug there. Sorry for the inconvenience, I hope you understand the reasoning above. Cheers