On Thursday, March 17, 2016 11:24:10 AM Mathias Hasselmann wrote: > Am 17.03.2016 um 10:01 schrieb Sorvig Morten: > > How about treating the coding guidelines as \internal documentation? > > We could then at some point build and publish it together with the > > rest of the \internal's. (suitably separated from the public user > > documentation) > > Actually having the Qt code style as public document proved to be > extremely useful in the past to quickly shutdown this inevitable and > highly annoying bike shed discussion about code style that happens at > the start of every other project. Also in the future I'd like to say: > > "We do a Qt based project and for consistency I propose to follow the Qt > code style: It's a good and proven style guide. Just read it > http://wiki.qt.io/Coding_Conventions and then focus on real problems."
I like this, public .qdoc makes it easier to make a case for Qt coding style among our customers. Regards, -- Sérgio Martins | [email protected] | Software Engineer Klarälvdalens Datakonsult AB, a KDAB Group company Tel: Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322) KDAB - The Qt Experts _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
