On Sat, Jun 25, 2016, at 02:40 PM, Bell, Richard S wrote: > There is actual IoTivity Wki Coding Standard page... > https://wiki.iotivity.org/iotivity_coding_standards > > Our team use the Bulk C++ Formatting - Artistic Style tool script > discussed on the page. > Visual Studio say it is using Artistic Style which I would hope is the > same the Bulk C++ Format but I have not actually used it. > > One caveat I noticed was the Eclipse IoTitity is not the same as the > Bulk. > I agree these should be the same and Eclipse should probably be changed > to conform to Artistic Style tool > My Team members who use Eclipse are required to run their code through > Artistic Style tool before checking in. >
In general I like the idea of consistent formatting, however in practice I've seen a few different workflows that tend to impact code formatting negatively. Eclipse had been a bit of a worst-case for this, where adding and removing line-breaks would automatically be done, and the only viable work-around was to append trailing comment markers to prevent the worst of it. That said, I've also worked on various projects (public and private) where we set up formatting configs for the more common tools out there including Eclipse, Emacs and Vi. Setting some of that up might be helpful. But again, my main concern is to be sure that we don't get a toolchain/config in place that is too rigid on the formatting and prevents keeping some flexibility to allow for legibility of code. -- Jon A. Cruz jon at joncruz.org
