While discussing what would be the steps of porting to Qt 5, boud said astyle (precisely, astyle-kdelibs [1]) would be a good option for post-processing. My update in this topic is a result of a quick test: - astyle-kdelibs is pretty nice, can break git blame/history on really bad formatting, so think twice - [1] is broken even for astyle ~ 2.02 (e.g. converts to const QString & foo, while const QString &foo) - [1] won't work at all for astyle 2.05 (I just upgraded to that) e.g. --brackets=linux doesn't exist - Eike Hein @ kde-devel IRC noted: it's expected that someone rewrites astyle-kdelibs using clang-format
My suggestion would be to stay away from the idea of autoformating until something improves. My idea is: my code isn't just mine but is expected to read by others, the same goes for history. [1] https://techbase.kde.org/Policies/Kdelibs_Coding_Style#Artistic_Style_.28astyle.29_automatic_code_formatting -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org Calligra Suite: : A graphic art and office suite - http://calligra.org Kexi: : A visual database apps builder - http://calligra.org/kexi Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek _______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
