| Summary: | Tool to see all members, including inherited (C++) | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Alexander Potashev <aspotashev> |
| Component: | Language Support: CPP (Clang-based) | Assignee: | kdevelop-bugs-null |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | Keywords: | junior-jobs |
| Priority: | NOR | ||
| Version First Reported In: | git master | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
More generalised: I think having a tool view that allows querying source code information wouldn't be too bad. The big problem is the query language / or the UI to allow defining the query. (Clang solves this with AST matchers, see here: http://clang.llvm.org/docs/LibASTMatchers.html). If anyone wants to work on this, please consider stealing concepts from Clang's AST matchers, it's super powerful, yet easy to work with. We could support part a subset of the AST matchers which would be used to filter our DUChain. There's also CQLinq which is quite powerful, from what I've seen on screenshots: http://www.cppdepend.com/cqlinq That is more geared towards usage by mere mortals in an IDE context. Actually, I think we should start with having a list of all members in a list similar to the one currently used for "show uses". A link to that could be added to the navigation widget and triggered from there. Should be fairly easy to add, I think. If anyone has questions, contact us on freenode#kdevelop IRC or our mailing list at kdevelop-devel@kde.org cheers |
Please add a tool to see all members, including inherited ones for a C++ class. It can be for example a tool view. For class B defined below this tool should list the members "x", "y", "f" and "g": class A { int x; void f(); }; class B : public A { int y; void g(); }; Reproducible: Always