https://bugs.kde.org/show_bug.cgi?id=369538
--- Comment #4 from Shawn McKenney <shawn.mcken...@emmion.com> --- Attached are some diagrams. It looks we should extend the TreeParser and the ClassImport classes with Clang equivalents. Then in the wizard we can select which parser to use. I agree with you, Ralf. I am going to start by creating some test cases. Should I just do that in my fork and send pull requests? Also, your llvmparser test case looks like what we should use to traverse the Clang AST. Those classes look like a good starting point. Is there any place I can stick these diagrams? I am a big fan of diagrams and will keep creating them for my own understanding. I'll be happy to organize them somewhere for others as well. I don't mind writing some technical documentation. Do we need to create some new Jenkins jobs for qt5? I don't see them anywhere. Comments/questions always welcome. -- You are receiving this mail because: You are watching all bug changes.
