![]() There is even more that can be done to make the process of mechanical refactoring with clang easier and faster. You will still do the same things, but with much faster development iteration to achieve the same result. This will take the mechanical refactoring workflow which is currently The idea as always is to hopefully have enough functionality in Clang itself that IDEs such as Qt-Creator, KDevelop and Visual Studio would be able to integrate these features using their own GUI APIs, making the simple tool I made obsolete anyway. Hopefully, once enough of the changes are upstream, I’ll be able to open source the tool. Of course, all of this requires changes to Clang upstream (for example to add the debugging interface) which was the point of my visit to EuroLLVM. The demos show all of the features you would expect from a point-and-click refactoring tool including exploring, feature discovery, debugging with in-source feedback, live source updates, experimental refactoring etc. Of course, given my KDE and Qt contribution history, I would only create a generic tree traversal class in order to implement QAbstractItemModel for it. I separated the textual output from the generic output independent traversal, which introduces the possibility of alternative output formats such as JSON. It was previously implemented in one class, ASTDumper, which had the dual responsibilities of traversing the clang AST and creating a textual representation of it. Nfmbx7fK26Įarlier this year I refactored the clang AST dump functionality. Glad to see Firefox used for demos (here, Stephen Kelly about refactoring using clang API) and in the audience. Great presentations at #EuroLLVM in Brussels. ![]() This talk is the one to watch if you are interested in using mechanical refactoring on your own code.įeedback was very positive from both talks, so I’m happy with that. In the ACCU presentation, the new demo content starts about 30 minutes in. My 1.5 hour ACCU presentation is a far-less-rushed presentation of the same tools and a repetition of some of the content at code::dive 2018. As this was my first LLVM conference, I am not already familiar with most of the attendees. #Qt creator refactoring plugin code#
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |