https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #6 from Ralf Habacker <ralf.habac...@freenet.de> --- (In reply to milasudril from comment #5) > I thought libclang would be usable. This way, new features would already be > implemented there. It may be usable, but noone has opened a working branch and tried to implement this until now. Umbrello always used a copy of the kdevelop c++ parser in the past and it seem to be the easiest to also reuse the clang based c++ language plugin from kdevelop (see https://techbase.kde.org/Projects/KDevelop4/ClangRoadmap#Why_Clang) Some of the Issues which need to be solved are: 1. umbrello needs to be refactored for running kdevelop clang language plugin 2. clang AST is completly different from kdevelop's c++ parser AST, which requires a rewrite of the AST to uml model binding (currently cpp2uml.cpp) 3. The recently used parser is very tolerant against incomplete c++ code, which is not the case for clang, which needs to be called similar to a compiler building the related source code. Incomplete code may come from missing include pathes or defines only available inside the build system of the imported source code files. This may require to run the parser similar to the coverity scan tools, which runs on top of a configured build system. Links: http://milianw.de/blog/katekdevelop-sprint-2014-let-there-be-clang http://llvm.org/devmtg/2015-04/slides/Funk_Libclang_Integration_KDevelop.pdf -- You are receiving this mail because: You are watching all bug changes.
